Is it possible to set data source precedence between serverless and ip address discovery schedule
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-30-2024 10:38 AM
Hi Everyone,
We are encountering an issue with fluctuating CPU count values; when the IP address discovery runs, it reports different values compared to the serverless Kubernetes discovery. We want to prevent this inconsistency by giving higher precedence to the IP address discovery. Is this achievable? Currently, the out-of-the-box data source precedence is available with ServiceNow, service mapping, SCCM, etc., but not between different types of discovery schedules like IP-based and serverless discovery. Can anyone provide insights.
Regards,
Srinija
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2025 12:20 AM
How do you know which CI's are created by serverless?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2025 04:27 AM
hi @Pratiksha ,
we match based on the stamp of the discovery schedule run time log and the server updated time log. if it is around same timeframe in the audit log, then we confirm this sever record is updated by the serverless discovery schedule.
Regards,
Srinija