How to determine if Foglight is not ingesting data?

Thank you for your reply.

• Dashboards is not an option for us. This has to be an automated solution.
• Agent health status is set to OK so we cannot use this as a flag.
• Which built-in Alert are you referring to? I am not able to find it.
• The server that is not sending data has the following entry in the Foglight log file:
  • 2024-03-20 10:27:52.037 VERBOSE [FglAM:IncomingMessageResponse[7]-16777] com.quest.glue.adapter.service.handlers.AgentCallbackResultHandler - Agent callback for FL_Agent FAKE_NAME completed successfully

We are not using email alerts from Foglight so our only options would be the Rest API or directly querying the FL tables.

Thank you.

Different agents have different Rules that generate alarms when they can't collect data.

• Agent Health State is generic and fires if the agent is not activateable (e.g. when the Agent Manager is offline)
• SQL Server agents: DBSS - Usability Connection Availability among others (see https://support.quest.com/kb/4293896/when-do-sql-server-availability-and-usability-alarms-fire)
• Infrastructure HostAgents (e.g. WindowsAgent): Host Monitored rule

You should look into  "Foglight Skills 101” Webcast Series to learn more about Rules/Alarms of interest. 

You can use the "Current Alarms" API to poll for the current alarms: https://support.quest.com/technical-documents/foglight/7.1.0/rest-api-reference-guide/3#422248

All APIs are restricted to a maximum number of objects returned by call, so if you expect more than 500 alarms, you may want to increase the limit so that you don't miss something important. https://support.quest.com/kb/4261411/rest-api-call-returns-501-objects-however-more-were-expected

I hope this helps.

- Jesus

Different agents have different Rules that generate alarms when they can't collect data.

• Agent Health State is generic and fires if the agent is not activateable (e.g. when the Agent Manager is offline)
• SQL Server agents: DBSS - Usability Connection Availability among others (see https://support.quest.com/kb/4293896/when-do-sql-server-availability-and-usability-alarms-fire)
• Infrastructure HostAgents (e.g. WindowsAgent): Host Monitored rule

You should look into  "Foglight Skills 101” Webcast Series to learn more about Rules/Alarms of interest. 

You can use the "Current Alarms" API to poll for the current alarms: https://support.quest.com/technical-documents/foglight/7.1.0/rest-api-reference-guide/3#422248

All APIs are restricted to a maximum number of objects returned by call, so if you expect more than 500 alarms, you may want to increase the limit so that you don't miss something important. https://support.quest.com/kb/4261411/rest-api-call-returns-501-objects-however-more-were-expected

I hope this helps.

- Jesus

Thank you Jesus.

We sometimes experience whole agent outages but that is rare. What troubles us are partial data ingestion or UI issues where the Instance View in the SQL PI screen does not show data but you do see the data if you click on individual databases.