A transaction index will only be created when you connect an agent to the APM Server which actually sends up transactions. So make sure to execute some requests to your instrumented application and wait for ~10s.
Thanks for the reply. I already generated some data on my application, but still cannot see any transaction indexes being created. I can see from the logs that metrics data in being sent to APM server, but still no transaction data.
I followed the troubleshooting page already and I could not find any of the typical errors in my setup.
I was wondering if you can give me some more hint?
Have you checked you are using one of the supported technologies? If yes, could you upload the agent debug logs of the startup up to when you make the first request to your application?
Thanks for the reply. Here is the logs from the agent.
(Just to recap: I only can see Metric events in my Kibana Discover tab, and it just creates Metric index. I only see the data/visualization for CPU/Memory and not any transaction data).
APM cloud Server : 6.6.2
APM attache agent: 1.4.0
============
2019-03-19 10:40:59.704 [apm-server-healthcheck] DEBUG co.elastic.apm.agent.report.ApmServerHealthChecker - Starting healthcheck to https://{APM-SERVER-ADDR}
2019-03-19 10:40:59.965 [Attach Listener] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - container ID is XYZ
.....
.....
.....
2019-03-19 10:41:01.071 [apm-server-healthcheck] INFO co.elastic.apm.agent.report.ApmServerHealthChecker - Elastic APM server is available: {"ok":{"build_date":"2019-03-06T14:11:42Z","build_sha":"sdadwkugugkfyfdsrsrs","version":"6.6.2"}}
....
....
....
2019-03-19 10:44:29.897 [apm-reporter] DEBUG co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Receiving METRICS event (sequence 12)
2019-03-19 10:44:29.898 [apm-reporter] DEBUG co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Starting new request to https://{{APM-SERVER}}/intake/v2/events
2019-03-19 10:44:30.002 [apm-reporter] DEBUG co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Scheduling request timeout in 10s
10:44:39.034 DEBUG [clojure-agent-send-off-pool-2] xy.service.job-service - - Job service master alive
2019-03-19 10:44:40.010 [apm-request-timeout-timer] DEBUG co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Request flush because the request timeout occurred
2019-03-19 10:44:40.016 [apm-reporter] DEBUG co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Receiving FLUSH event (sequence 13)
2019-03-19 10:44:40.022 [apm-reporter] DEBUG co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Flushing 1371 uncompressed 592 compressed bytes
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.