Set cmdb ci attribute based on discovered mid server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2025 01:36 PM
What is the best way to set a custom field on the cmdb_ci table based on the processed mid server? I am leaning towards setting a "Set Parameter Value" step at the discovery pattern. Are there any other ideas? I cannot do a business rule, it has to be set at the time of discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2025 11:05 PM
The best way is to use the "Set Parameter Value" step in the Discovery Pattern to map ${mid.server} to your custom field. Other options include modifying the Discovery Sensor Script, using ECC Queue Data Processing, or customizing a Process Classifier, but the pattern method is the simplest and most efficient.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2025 07:28 AM
I am from an ITSM background and trying to create a step in discovery pattern. mid.server is do not show up as. a value to chose in the set parameter value step. Instead I did a parse command output to run "echo %USERDOMAIN%" command. Now stuck at figuring out how to get the output copied to a temp variable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2025 05:46 AM
1. Use "Set Parameter Value" in Discovery Pattern – Map the MID Server to the custom cmdb_ci field during discovery.
2. Modify Identification & Reconciliation Engine (IRE) – Adjust transformation rules to update the field.
3. Custom Script in Discovery Process – Use a Processing Step Script to set the value dynamically.
4. Discovery Event Rule – Configure an event to update the attribute after discovery.
