Skip to content

Commit c9d9347

Browse files
committed
Add expected APM server response logs to troubleshooting
1 parent d262712 commit c9d9347

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

docs/troubleshooting.asciidoc

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,19 @@ Each request should at least add some lines similar to these in the logs:
4646
----
4747

4848
If you don't see anything in your logs,
49-
the technology stack you are using is probably not <<supported-technologies,supported>>.
49+
the technology stack you are using is probably not <<supported-technologies-details,supported>>.
50+
51+
After that, you should see logs indicating that the agent has successfully sent data to the APM server:
52+
53+
----
54+
[apm-reporter] DEBUG co.elastic.apm.report.ApmServerHttpPayloadSender - Sending payload with 1 elements to APM server http://localhost:8200
55+
[apm-reporter] DEBUG co.elastic.apm.report.ApmServerHttpPayloadSender - APM server responded with status code 202
56+
----
57+
58+
If the APM server responds with a 400,
59+
it could indicate JSON validation errors.
60+
In that case,
61+
please turn on `TRACE` logging and send us the logged JSON payload.
5062

5163
[float]
5264
[[trouble-shooting-debugging]]

0 commit comments

Comments
 (0)