Discovery Pattern Serial Number References
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
How come most of the OOTB patterns that create a reference to the cmdb_serial_number table set the column name "configuration_item" when the column doesn't exist on the table (the reference is named "cmdb_ci")? Am I missing something?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@hcallen Can you please provide the exact Pattern you are looking at? When I checked the 'Windows OS - Desktops', the mapping is to cmdb_ci.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@Vijaya_Mnpram
I'm looking at the "Next Generation Palo Alto Firewall" pattern. Also, when looking at the "Windows OS - Desktops" pattern, the column name is "non_ci" (which doesn't exist on the Serial Number table too). As far as I know, these patterns have never been touched.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@hcallen I guess, these column names are for the Result tables created ($serial_computer in the screen shot). They are not the column names of neither parent nor child.
I entered debug mode with a Windows Desktop IP address, and the Serial number is picked even before establishing this reference. When 'Generate Playload' button is clicked on, the serial number is already picked ( in the step 2.14 Library).
I guess for the 'Next Generation Palo Alto Firewall' pattern also, you can enter the debug mode with a sample value and check where exactly the Serial number is picked up. I don't have any sample to check it.
