posasterling.blogg.se

The secret token in the request header doesn’t match the configured in the APM Server. Setting in the APM Server, and adjusting relevant settings in the agent. If events are too large, you should consider increasing the max_event_size Each event is sent as its own line in the HTTP request body. HTTP 400: Event too large editĪPM agents communicate with the APM server by sending events in an HTTP request. See the agent/server compatibility matrix for more information. The most likely cause for this error is using incompatible versions of APM agent and APM Server. HTTP 400: Data decoding error / Data validation error edit

The agent documentation for details on what is automatically instrumented.ĪPM Server currently relies on Elasticsearch to create indices that do not exist.Īs a result, Elasticsearch must be configured to allow automatic index creation for APM indices.

The response code to narrow down the possible causes (see sections below).Īnother reason for data not showing up is that the agent is not auto-instrumenting something you were expecting, check If you see requests coming through the APM Server but they are not accepted (response code other than 202), consider Particularly, if you are using Docker, ensure to bind to the right interface (for example, setĪpm-server.host = 0.0.0.0:8200 to match any IP) and set the SERVER_URL setting in the agent accordingly. If no requests are logged, it might be that SSL is misconfigured or that the host is wrong. To see if the agent can connect to the APM Server, send requests to the instrumented service and look for linesĬontaining in the APM Server logs.