What are Webhooks and why do they matter to SCOM?
Webhooks what are they?
A Webhook is an API that delivers data from applications when an action or event occurs. When an event is triggered within the source site, it is seen by the Webhook, which collects the data and sends it to the desired application or URL in the form of an HTTP request. Webhooks are also instant, triggering the delivery of data in real-time, this makes them faster and easier to implement than other methods, like polling.
What are Webhooks used for?
This means Webhooks are the ideal way to synchronize different applications, share information and deliver notifications when events occur.
Let’s look at some real-life examples of how Webhooks are being used:
PayPal uses Webhooks to tell your accounting app when your contacts make a payment to you.
Shopify utilizes Webhooks to keep your information up to date, so you don’t have to enter your details manually for each new transaction.
MailChimp uses Webhooks to automate the signup of users from your website to your newsletter.
What are SCOMs native options for delivering data?
When it comes to SCOM unfortunately, its data delivery options are quite basic and somewhat outdated. There are three ways to send notifications when an event is triggered, each of which has its own merits and pitfalls:
1) Email – these are simple to set up in SCOM, but this method is not always effective as you are reliant on the person at the other end reading the email and taking the required action. This can result in the recipient of these notifications becoming overwhelmed by emails too!
2) Text Message (SMS) – this method is trickier to set up as you’ll need to find a third-party tool to connect your systems. We recommend this method is only used to send critical alerts or alerts of high importance, to ensure you get cut through.
You may also find your stakeholders are moving away from traditional communication channels, such as email and text, and will be far more engaged if these notifications are delivered into their day-to-day tools and applications (e.g. Google chat, Twilio, etc).
3) Command Channel – this gives you the flexibility to connect SCOM to anything, but it is old-fashioned and code-heavy, making it the most challenging option to implement.
If these options are not appealing to you or you have a simple requirement in mind, then we recommend you give our free PowerShell Authoring MP a try.
What other options are there for SCOM?
There are a few pre-built tools on the market that can also help you connect SCOM with your other IT systems:
1) Kelverion System Center Orchestrator (SCORCH) discovers the configuration of your targeted tools and provides a simple forms-based interface as the foundation for a runbook design. So, whilst it is possible to integrate SCOM with several other IT systems you are limited by the number of connection packs available (~40), most of which are on-prem. Plus, setup can be time-consuming, as this is a clunky process requiring you to bolt together quite a few tools and configure some of the data yourself. You will also need a SCORCH license before you can get started. So, although the final product offers a reasonable level of integration and automation, it is certainly not user-friendly.
2) Au2mator provides a flexible framework, with question-driven workflows, but it only supports four automation platforms: System Center Orchestrator, Azure Automation, PowerShell, and System Center SMA. So, not only is its application limited but if you simply want to transfer SCOM alerts to/from other systems, you may find this tool overly sophisticated or unnecessary overhead.
3) DIY Management Pack you can always write your own MP tailored to your exact requirements, but this is time-consuming and technically challenging. This option is suited to people with authoring expertise or a very specific set of needs.
4) Webhooks come in two forms to enable data to be pushed in and pulled out of SCOM:
Outbound: sends alerts from SCOM and pushes them into other platforms as incidents, messages & tickets, or to trigger automations.
Inbound: receive messages from other platforms into SCOM, to raise alerts & events.
Connection Center the simplest way to connect SCOM
Webhooks are the most effective and easy way to connect SCOM to your other tools, putting SCOM at the heart of your monitoring operations.
As experts in SCOM integrations, Cookdown has developed both Inbound and Outbound Webhooks so you can synchronize data flowing in and out of SCOM, with your other monitoring tools and communication applications.
Connect SCOM to anything, anywhere!
Getting set up couldn’t be easier! Simply configure Webhooks in your destination system and set up Cookdown’s Connection Center using the UI, and you’re ready to start sending alerts and receiving data – absolutely no coding required!
To find out more about our Webhook integrations click here or give it a test drive with our FREE 30-DAY TRIAL.
Make SCOM better connected
We don’t just specialize in Webhooks we also have a long list of bespoke integrations for SCOM. So, if you are looking to modernize your connection architecture then check out our integrations for:
