So CD can be disabled if it tries to create not present items incorrectly. And the only way to re-enable CD is to run update MF.
You should check the DA karaf.log* files and see if you can find a message like:
Change detection for MF <mf internal name> on device <itemID> is disabled.
So get the itemid of the device you ran update MF on, and search karaf.log* files for that itemid and see if returns a message like above.
Original Message:
Sent: Feb 03, 2023 07:40 AM
From: Praveen Venkatesan
Subject: Change detection completion status
Yes @Michael Poller there was an alias name update in Interface and it didn't picked for 3 days ,once after manual update it got updated . There are any logs captured for CD somewhere in DA?
Original Message:
Sent: Feb 02, 2023 04:24 PM
From: Michael Poller
Subject: Change detection completion status
CD schedules for locked default Monitoring Profiles are not configurable.
CD schedules for custom user created Monitoring Profiles are configurable.
Extending CD schedules to a 3 day time frame wouldn't necessarily be recommended. It would likely result in a longer delay than desired for device update changes being found and made in NetOps.
I wonder why the concern. Are there problems you suspect are related to this area?
Original Message:
Sent: Feb 02, 2023 04:18 PM
From: Pankaj Udhas Katigar
Subject: Change detection completion status
CD is default to 24 Hours and I don't think it can be changed.
Original Message:
Sent: Feb 02, 2023 10:26 AM
From: Praveen Venkatesan
Subject: Change detection completion status
Yes i agree with you ,but i have 10 K devices and CD is set to 24hrs .. I hope only few devices/interfaces are picked in those cycle and some are skipped . My plan to extend the CD 3 days once so it can cover all devices. There is any limitations on number of devices for run?
Original Message:
Sent: Feb 02, 2023 10:17 AM
From: Jeffrey Pinard
Subject: Change detection completion status
There should be an event on each device for each MF run through change detection (CD), describing is there was any changes or not.
Note: CD randomizes all the devices across the 24 hrs, so we are not doing all the work during a small period. CD starts 24 hrs after it's configured, or DA restarts.
Note: You will only see MF/VC Last discovered time change when a new VC is determined. You will only see Last discovered time change on a component if it was discovered new or updated during CD.
Original Message:
Sent: Feb 02, 2023 10:01 AM
From: Praveen Venkatesan
Subject: Change detection completion status
All,
We have enabled change detection for metric families for every 24hrs once ,How can i confirm in PM whether it has validated for all discovered devices/interfaces/other components .