FineOps provides Health Monitoring and Tracing functions to help you (the admin) pinpoint performance issues that occur when users view and analyze dashboards/reports.
This document describes how to use FineOps to pinpoint performance issues for FineReport templates/FineBI dashboards/FineDataLink tasks based on usage scenarios.
1. It was impossible to measure and pinpoint issues.
2. The process depended on passively awaiting users' feedback due to the lack of proactive monitoring mechanisms.
Troubleshooting:
Access Health Monitoring.
If the value of Application Performance Index (Apdex) is too low, it indicates overall system slowness.
If the value of Request Success Rate is too low, it indicates system failures.
Check Service Response Time and Data Response Time to determine whether system slowness results from data response delays or other factors.
Effect:
1. You (the admin) can proactively check whether system slowness occurs via Health Monitoring instead of passively reacting to users' feedback.
2. The actual user experience is presented accurately in data.
Check the monitoring dashboards to see if garbage collection (GC) events occurred or if CPU usage peaked. For details, see System Resource Monitoring.
You can pinpoint issues, for example, GC problems, rapidly.
1. The process depended on passively awaiting users' feedback due to the lack of proactive monitoring mechanisms.
2. You needed to analyze logs by yourself.
1. Check for anomalies through dashboard charts proactively instead of passively reacting to users' feedback. For details, see System Health Monitoring.
2. Navigate to First-Screen Trace for analysis.
View which reports the user accessed during that period, examine the user's query latency, and so on.
If a first-screen trace was highlighted in yellow, its duration or the duration of its associated traces exceeded 10 seconds.
3. Navigate to Trace through jumping for in-depth analysis of slow requests (recommended), where you can pinpoint issues such as network fluctuation, database performance issues, configuration database issues, resource complexity, and resource insufficiency.
It enables tracking the real performance the user experienced and reduces troubleshooting time to within 10 minutes.
1. Check for requests with poor performance (response time > 10 s) through dashboard charts proactively instead of passively reacting to users' feedback. For details, see System Health Monitoring.
View the users who accessed the specific report and the usage latency.