Why APM Insight monitor's Apdex, Response Time, and Throughput not showing When app has only Background Transactions (BGT)?
Monitor is UP, Background transactions visible, but Web shows "No data" and KPIs (Apdex, Response Time, Throughput) are missing.
Clarification
- Background Transactions (BGT) are being captured based on traffic
- KPIs (Apdex, Avg Response Time, Throughput) apply only to Web Transactions
- If the application has no HTTP endpoints (worker/batch services), these KPIs will show "-"
This is expected behavior & a known limitation.
BGT-specific KPI visibility is planned in upcoming releases.
BGT-specific KPI visibility is planned in upcoming releases.
View BGT metrics at: APM → Your APM Insight Application or Instance → Transactions → Background
Next Steps: Custom Instrumentation
If BGT auto-discovery is not capturing your application methods (e.g., short-lived JVMs, custom frameworks), use Custom Instrumentation.
Configure via UI: APM → Your APM Insight Application or Instance → Monitor Actions → Edit → Custom Instrumentation
1. Class-Level Instrumentation (Recommended)
Instrument specific classes and methods:
Syntax: package/ClassName : method1, method2 : ComponentName
Example:
| Configuration | Description |
|---|---|
| com/manageengine/apm/BatchProcessor : runJob, processData : BatchJobs | Specific methods with component name |
| com/manageengine/apm/DataSync : syncRecords : DataSync | Single method with component name |
| com/manageengine/apm/ReportGenerator : : Reports | All methods in class with component name |
| com/manageengine/apm/Scheduler : : | All methods in class (default component) |
2. Package-Level Instrumentation (Use with Caution)
Instrument all classes under a package:
Syntax: package/.* : : ComponentName
Example:
| Configuration | Description |
|---|---|
| com/manageengine/apm/batch/.* : : BatchProcessing | All classes under com.manageengine.apm.batch |
| com/manageengine/apm/workers/.* : : | All classes under com.manageengine.apm.workers (default component) |
⚠ Warning: Package-level instrumentation is not recommended.
The agent will instrument all methods in all classes under that package, which may cause:
- Extra CPU and memory overhead
- Many uninteresting methods captured
- Lengthy traces that are hard to analyze
Use only for studying code flow or during troubleshooting.
Reference
Tip: Prefer UI-based configuration (Monitor Actions → Edit → Custom Instrumentation) over editing
instrumentation.conf directly.
New to ADSelfService Plus?
Related Articles
APM Insight Troubleshooting - FAQs
Monitor Addition - FAQs 1. How to add an APM Insight Monitor? After you deploy the APM Insight agent in your Application Server with suitable Applications Manager credentials in the apminsight.conf file, APM Insight monitors will automatically be ...Self monitor Applications Manager using APM Insight Java Agent
Applications Manager is built with Java, hence we can monitor it using APM Insight Java Agent to measure it's performance continuously, which can be very much useful. Setting up APM Insight Java Agent Follow the below steps to download and set up the ...Uninstrumented Block of Code - APM Insight
In the traces tab --> Slowest Method Calls and Count we show if you find Un-instrumented block of code the reason is as follows: Basically, What is un-instrumented block of code in APM Insight? By default, APM Insight agent monitors known frameworks ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...DNS Monitor - Troubleshooting
Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...