IDM currently publishes ProcessedOperationsCounts in cn=monitor but no information about a driver's cache. When queried via dxcmd for "Get driver cache statistics" IDM return both the ProcessedOperationsCounts along with the age and number of transactions in a driver's cache. Especially the age of the oldest transaction and the total number of transactions in the cache are vital in determining the health of a driver.
If not in cn=monitor, why have cn=monitor at all? Is that not the place to monitor the processes? How do you decide which is 'monitor' worthy (Not sponge) and which should be in longer term reporting/storage. (Which is actually a fair and hard question to answer).
This example though might provide a simple criteria... cn=monitor would be for things that a alerting/paging/monitoring solution might need. I.e. Service up/down. Cache filling faster than it is emptying. Cache is older than X days.
Whereas, how many PRDs have been run this week makes more sense in a Reporting/IDI style solution.
If not in cn=monitor, why have cn=monitor at all? Is that not the place to monitor the processes? How do you decide which is 'monitor' worthy (Not sponge) and which should be in longer term reporting/storage. (Which is actually a fair and hard question to answer).
This example though might provide a simple criteria... cn=monitor would be for things that a alerting/paging/monitoring solution might need. I.e. Service up/down. Cache filling faster than it is emptying. Cache is older than X days.
Whereas, how many PRDs have been run this week makes more sense in a Reporting/IDI style solution.
Top Comments