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.

View BGT metrics at: APM → Your APM Insight Application or Instance → Transactions → Background

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

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)

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:

Use only for studying code flow or during troubleshooting.

Tip: Prefer UI-based configuration (Monitor Actions → Edit → Custom Instrumentation) over editing instrumentation.conf directly.