We're Hiring!
Take the next step in your career and work on diverse technology projects with cross-functional teams.
LEARN MORE
Mountain West Farm Bureau Insurance
office workers empowered by business technology solutions
BLOG
3
4
2019
3.1.2023

Writing to the Windows Application Log During a Beekeeper Execution Job

Last updated:
9.16.2020
3.1.2023
No items found.

Using a PowerShell validation during any of the Beekeeper Execution Job phases, you can write information to the Windows Application Log. This helps enable discovery for SCOM. The Event Log Validation Pack is a collection of PowerShell validations that you can customize in your environment.

Learn how to implement this, including downloadable Validation Pack and code snippets, in this blog post. For more information about Beekeeper patching automation software, view the product page.

This snippet of code illustrates how a new event log source is created and writing an event using that source:

Using custom event IDs, event type, and message text, each of the validation task phases can be set. Remember to use the "#!nodename!#" mnemonic in your scripts to get the name of the node during the Beekeeper execution job – discussed in the Beekeeper v5 Manual on page 87.

You can download this Validation Pack here.

To import the Validation Pack, you can use the Import-ValidationTask.ps1 in the Scripts directory of the Beekeeper v5.1.0 zip file.

From a PowerShell prompt (replace bkprdev03 with the name of your Beekeeper server in the URI parameter):

Adding the event log validations to your Application Groups, DAGs, or Windows Failover Cluster is done from the Servers and Clusters tab. Select the appropriate group type and the click the Edit button near the middle of the screen for your server group.  The pencil icon will edit the definition of the specific group.

To select the appropriate validation task from the Available area, you click the green “+” and it will add it to the Configured area.  Select the correct phase and you are done when you click.

Once the events are in the Windows Application Log, you can use SCOM to alert to these events using the custom event source – “Beekeeper”.  You would need to create an event collection rule for these events.  You may want to create an event view as well.

Recent Blog Posts

lunavi logo alternate white and yellow
3.27.2024
03
.
27
.
2024
Utilizing Bicep Parameter Files with ALZ-Bicep

Ready to achieve more efficient Azure Deployments? You can use Bicep parameters instead of JSON which opens new opportunities for deployment. Let Lunavi expert, Joe Thompson, show you how.

Learn more
lunavi logo alternate white and yellow
3.26.2024
03
.
04
.
2024
Anticipating Surges in Cyber Attacks and Bolstering Your InfoSec Defenses in 2024

Learn how to navigate 2024 with the right InfoSec defenses to protect your organization against a rising number of cyber attacks.

Learn more
lunavi logo alternate white and yellow
3.26.2024
01
.
03
.
2024
Microsoft Copilot is Re-Shaping the Innovation Frontier

Microsoft 365 Copilot has been released, and it's changing the way we work. More than OpenAI or ChatGPT, read how Copilot can seamlessly integrate with your workflow.

Learn more