Set up APM¶
About APMs on MedStack Control¶
While many APMs are capable of running on MedStack Control, this guide discusses setting up APMs that are installed as libraries in the application layer which prevents them from needing access to the Docker socket file if running as a sidecar service.
Capabilities¶
Since supported APMs are installed as libraries in the application layer, they are most suitable for measuring application-side performance like the duration of queries and responses, internal processes, etc.
Limitations¶
The Docker socket file (docker.sock) cannot be mounted as a service volume, thus the APM will not have access to Docker nodes, services, nor container performance metrics like CPU & memory utilization, storage consumption, or I/O.
Common APMs¶
There are many APM providers in the market. Here are some of the providers we find teams running applications on MedStack Control commonly use.
Datadog¶
Datadog is a powerful and easy to install APM that works well in clusters on MedStack Control because the APM is installed in the application layer rather than as a sidecar service.
You can install the Datadog APM for many different libraries. Some common libraries include:
You can check out their full list of libraries if the one relevant to you is not listed above.
New Relic¶
New Relic is a powerful and easy to install APM that works well in clusters on MedStack Control because the APM is installed in the application layer rather than as a sidecar service.
You can install the New Relic APM for many different libraries. Some common libraries include:
You can check out view their full list of libraries if the one relevant to you is not listed above.