Install Status for Application CIs discovered using custom pattern

[NirmalSharma]

I have a scenario of using a custom pattern to discover an application TIBCO Rendezvous. I am able to discover it successfully, "no issues". However when software is not available anymore discovery is not setting its install status as 'Absent'[which is my understanding that it should do]. I checked the deletion strategy but I could not find any record for its class as well for the pattern. N

Can someone help me understand what might be wrong. Expectation is that install status should be set to absent if discovery is no more able to find it.

#ITOM, #Discovery #Pattern

[pavani_paluri]

Hi @NirmalSharma ,

This is the Expected Behavior, when a CI (Configuration Item) is no longer discovered, the Install Status should be set to "Absent"
This is controlled by the Deletion Strategy associated with the CI class or pattern

Verify CI Identification: Ensure your custom pattern correctly identifies the CI and sets the install_status field
If the pattern doesn’t set install_status, Discovery may not update it when the CI is missing. In your pattern, explicitly set install_status to Installed when discovered
Check Discovery Log and ECC Queue: Review the Discovery Log for the relevant run. Look for messages indicating whether the CI was skipped, ignored, or marked absent
Pattern Scope and Class Mapping: Confirm that your pattern is mapped to the correct CI class. If the class is not properly linked, deletion strategy won’t apply. Ensure your pattern’s output class matches the class in the deletion strategy

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P

[NirmalSharma]

Thankyou @pavani_paluri  for your attention to this.

I made patten to set install_status as 1 by taking a reference of https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0829866 and did rescan the server. It set the install status to 1 which I could verify in CMDB 360. However it did not touch the other threes which I am expecting to be marked as absent by this pattern.

I would assume it will not do it for the older CIs but will mark current CIs as absent when they are not discoverable anymore. Please help putthing more light to this area.

I checked ECC Queue and Discovery log and could not notice anything for these CIs like skipped, Ignored or Marked Absent. Only message I see is below:

Information

Launching Pattern for CI type cmdb_ci_appl_tibco_message, skipping creation of Shell CI

your last point it a little tricky.

in the pattern I see it is correctly link to the Class but still I do not see any deletion strategy create for this. See below..

[srinija_itom]

hi @NirmalSharma , 

Here are my thoughts, I think you need to create new Ci deletion strategy for this pattern on your custom pattern. To configure this Navigate to tracked files on the pattern or navigate to sa_ci_to_pattern to create a new record to mark these CI's as absent. 

If you found this answer as insightful, please accept solution or mark it as helpful.

Regards, 

Srinija Amisthapur

ServiceNow Rising Star 2025 ⭐

Certified Technical Architect

[NirmalSharma]

Can you please help me understand as what is the configuration file of the pattern? Configuring this will delete the records created by this pattern not available anymore? Do you mind helping me understand this in bit more detail pls?

read this https://www.servicenow.com/docs/bundle/xanadu-it-operations-management/page/product/discovery/task/t... and noticed one line " Configure the system to collect information about changes in configuration files belonging to a configuration item (CI). ".

I want to understand "configuration files belonging to a configuration item (CI). " in a bit more details as what are the configuration files?