12 Sep 2024 01:31 PM - last edited on 13 Sep 2024 07:18 AM by MaciejNeumann
When a problem gets created for an OS service stopping it shows the actual server name, not the ID. However, the event that gets created for this contains the host ID, not the actual name. Is this expected? This results in our ServiceNow tickets showing the exact information you see in the problem card except that we get the host ID which is useless for 99% of our users.
Solved! Go to Solution.
13 Sep 2024 10:59 AM - edited 13 Sep 2024 10:59 AM
Hi,
Have you try to add properties to OS service configuration? I can see some placeholders, maybe this will work:
If not, you can explore other placeholders, those properties should appears in event.
Best regards
24 Sep 2024 02:07 PM
I guess I could try adding that but my thing is why should I have to? Why can't an event just by itself contain all of the relevant information? Why pass in the host ID which ends up showing in the ticket, that ID is useless in this situation. Do I care about the host ID of the impacted host? No.
We also just had a situation where for whatever reason we didn't have the hostname tag populated on a windows host, or at least that value was not passed into the event that got created for the service stopping. Because of that the automation we have in place failed because today a basic event for os services does not have the actual server name of the impacted host, so we have to grab that value from the auto tag rule we have in place.
I suppose because of this situation that occurred I will be be looking more into this property but I again go back to the why. Yes its great there is that capability but it just seems to be unnecessary overhead, having the server name in the event should have been in place from day 1.
24 Sep 2024 02:28 PM
Hi,
I understand you but this is only way I see it today.
I think that is already in roadmap, but you can always raise a product idea.
Best regards
13 Sep 2024 11:11 AM
Hi ,
You can update below property in Settings >> Monitoring >> OS Services Monitoring
and you customize your Problem card event tile as well:
dt.event.title: {host.name}--Service--{dt.osservice.display_name} is in undesirable {dt.osservice.status} state