Agents are written in the same language as your service. Monitoring a new service requires installing the agent and configuring it with the address of your APM Server, a secret token (if necessary), and a service name.
The Go agent automatically instruments Gorilla and Gin, and has support for Go’s built-in net/http and database/sql drivers.
The Java agent automatically instruments Servlet API, Spring MVC, and Spring Boot out of the box.
The .NET agent automatically instruments ASP.NET Core applications, while .NET Framework applications can be instrumented with the public API.
The Node.js agent automatically instruments Express, hapi, Koa, and Restify out of the box.
The Python agent automatically instruments Django and Flask out of the box.
The Ruby agent automatically instruments Rails out of the box.
Real User Monitoring (RUM) captures user interactions with clients such as web browsers.
Check the Agent/Server compatibility matrix to ensure you’re using agents that are compatible with your version of Elasticsearch.
Choose a service nameedit
The service name is used by Elastic APM to differentiate between data coming from different services.
Elastic APM includes the service name field on every document that it saves in Elasticsearch. If you change the service name after using Elastic APM, you will see the old service name and the new service name as two separate services. Make sure you choose a good service name before you get started.
The service name can only contain alphanumeric characters,
spaces, underscores, and dashes (must match