Monitor Troubleshooting¶

Introduction¶

This article will introduce how to troubleshoot common monitor issues:

• The monitor does not generate events.
• The monitor has events, but no message notifications are being pushed.

Prerequisites¶

• Requires an account with permissions to create monitors in Guance.
• Requires backend management permissions for monitoring.

Troubleshooting Steps¶

Step 1: Log in to the Func platform to query the issue¶

• Obtain the Func login address via Launcher

• Log in to your func platform (built-in system login).

You can consult Guance support tickets for the account.

Step 2: Check if the Func worker queue is blocked¶

• Check the overview to see if worker-8 and worker-9 have too high a load or if the work queue is too long.

Solution:

• Increase the number of replicas for worker-8 and worker-9. If the work queue remains blocked, continue troubleshooting with the next steps.

Note: When increasing the number of worker-8 replicas, be mindful of the query pressure on the log engine and time-series engine.

Step 3: Create a test monitor¶

• Log in to the Guance console.

• Select "Monitoring" - "Create Monitor" - "Threshold Detection."

• Detect Metrics:

M::`cpu`:(COUNT(`usage_guest`)) BY `host`

• Trigger Condition: Critical Result > 0

• Event Title: test

• Event Content: test

• Alert Strategy: Choose the strategy you have set up.

• Save

Step 4: Obtain the automatic trigger configuration ID¶

• Log in to the Guance console, select "Monitoring" - click the monitor name link to obtain the automatic trigger configuration ID.

Step 5: Modify FUNC system settings¶

• Open system settings and enable "Local Function Task Logging."

Step 6: Query FUNC execution records¶

• "Manage" - "Automatic Trigger Configuration" - "Select Display All" - "Enter the ID from Step 4" - "Confirm Search."

• Configure automatic triggers and set "Task Record Retention" to 20.

• Manually trigger the detection.

• You can view detailed error information through "Recent Executions."

Step 7: Restore Configuration¶

• Disable "Local Function Task Logging."
• Restore the default "Task Record Retention."