Hello,
We are running Monitor 2023.2. I checked the Logs in Monitor and saw there were pages of Severe level entries filling up quickly.
What causes the Monitor this error and how to fix this ?
Thank you!
Anthea
Hi Anthea,
Can you tell which component the failing observers are associated with? Perhaps the component is not available to be monitored which is causing the observers to fail. If this is the case, I suggest disabling the observers in question until the component is reachable again.
Josh
Hi @GeoJosh the log did not indicate which component is not available. I tried to change the Log setting to verbose and there is not much information. Is there a way I can check?
Thanks!
If you expand one of the log entries in your screenshot, you should get more details on why the observer failed and possibly what component it belongs to. For example, in the screenshot below, my observer with ID 173 is failing because the component is not reachable.
Are you not able to see the ID or details of the observer that is failing?
@GeoJosh oh boy not sure why I missed that expand icon in the Log. I got it now thanks !
@JamesBratton take the ID in the log and login to Postgres DB and query the observers table to find component_id related to the ID.
Then query the components table with the component_id in question :
Sample:
SELECT * FROM public.components
where id = 3562021
Hi @GeoJosh . Can you help me understand how to fix my Discover Observer? The observer has an error and the log details state ["Failed to create the metric 'agm-machine-name.domain'. A metric by the name 'agm-machine-name.domain' already exists."]
Thanks for any advice!