Binding process events to application CIs (MSSQL, Tomcat, Postgres etc.)

Jim Palmer
ServiceNow Employee
ServiceNow Employee

‎11-28-2024 03:00 PM

Community,

 

This is a long running challenge in the event management space, but i haven't seen anything specific as a leading practice so i thought i'd ask about what other people have done in this situation.

 

Assume you receive an event from a 3rd party monitoring system for a MS SQL service offline (service, not process - Windows not *nix).

therefore you will get a short hostname, the process name, that it's part of a 'MSSQL' monitoring profile and not much else; definitely not the instance name/port/command etc that would directly bind it using a CI identifier.

 

As far as the monitoring is concerned, it's fired from the host - but the impact is on the MSSQL instance which is managed by a different team to the host.

 

How have other people managed this?

I've written field mappings to interrogate the relationship table and get a 'best' match to the MSSQL instance [cmdb_ci_db_mssql_instance]- considering the service name can't be directly linked to a specific instance - but has anyone done anything more elegant? Considering you can have multiple SQL instances on a single host (though it would be quite the edge case to have 2 SQL instances on one host managed by different support teams).

Labels:
0 Helpfuls
  • 423 Views
1 REPLY 1

marcguegueniat
Kilo Sage

‎12-05-2024 12:06 AM

Hello,

To map events to application CIs, you have to switch the Binding method in the binding tab of your Event rule.

Check the "Override default binding" checkbox and then select "CI Identification"

Then select your target class like cmdb_ci_db_mssql_instance

Then you get to provide an input for each of the identification fields according to the IRE identification rules of your target class.

Regard,

0 Helpfuls