In Netcool Operations Insight v1.6 (NOI 1.6), weâ€™ve added a host of new capabilities to help you manage virtually any event source (including cloud) with Netcool.
The first of these, is Connect, Observe, Ingest. This article digs a little deeper into this subject.
Netcool has always been an industry leader at gathering data from many kinds of different sources. With 130+ integrations, we connect, observe and ingest events ranging from Network devices to application performance management solutions. Here’s a list of everything NOI can manage.
So Netcool knows the value of the old adage “you cannot manage what you do not measure.”
How do you get a holistic view in today’s new hybrid and multi-cloud environment? The end-to-end(E2E) service may include on-premise equipment, private cloud and public cloud…
Well from a monitoring and management perspective, you need to measure (or monitor) all types of data at your disposal including:
And this is something NOI has done easily for years.
Managing in today’s environment
But today’s environments are in a state of constant change. Of course you need to monitor the current state of the service. But also you need to be able to investigate historic incidents and be able to correlate events, topology and metrics as they existed at that time.
We are planning a future blog on this very subject (Get Relevant Context) as part of the NOI 1.6 blog series.
Cloud based sources
Now as well as our traditional sources, we’ve made it easy to integrate with Cloud based sources.
Let’s illustrate this with an example. Say, you’re responsible for central operations for “SparklingUnicorn”. Here’s the situation:
- Some teams are using several Cloud based services to develop their apps.
- They’re also using some traditional infrastructure.
- Your team provides first level support for those apps.
- You need to get overall visibility on both the traditional infrastructure and the new Cloud sources
Let’s assume, for example, that part of your E2E service includes a portion of it running on Azure. With our new Cloud based sources, you can easily configure ingestion of Azure events into NOI 1.6.
It’s as easy as A-B-C. Here’s how.
In CEM, go to Administration->Integrations->Configure an Integration, select the Microsoft Azure tile and press Configure
Next, choose a unique name for this integration, e.g. SparklingUnicorn_Azure. You will also notice that CEM has generated a unique webhook URL for your subscription. If any client sends an Azure event to this webhook, CEM will process it accordingly.
Note: A webhook is essentially a HTTP endpoint and is a way for one app to provide other applications with real-time information.
In the last step, you need to copy this webhook, go to Azure portal, portal.azure.com and add the webhook URL to a Classic alert rule or add the webhook URL into Azure Alert Action Group.
Then, when Azure generates an event, it will be sent to CEM webhook URL, where it will be normalised into a common incident format and displayed in the Incident View.
I told you it was easy.
Oh, one more thing. Although we have 30+ out-of-the-box cloud integrations, you can easily configure your own
integration if it supports a webhook, via a simple UI. Read about how to integrate NOI and Sysdig using a generic webhook.
Find out more
In this blog post I discussed how to Connect, Observe and Ingest both traditional and cloud-based sources, demonstrating how to manage virtually any event source (including cloud) with Netcool. It’s as easy as A-B-C. I also shared a detailed step-by-step guide showing you how to integrate with any source that supports webhook via a simple UI.
Do contact us if you have any questions.
- Discover how to modernize IT operations management (ITOM) with artificial intelligence operations (AIOps) and hybrid deployment options at the IBM ITOM site.
- For details and pricing information about IBM Netcool Operations Insight (NOI), visit the IBM NOI site
- NOI 1.6 released on June 31 2019. Read more about the new features of NOI 1.6
- Explore NOI 1.6 further in this series of blogs from the technical team who created this release.