Ingesting metrics
Install the NevTan monitoring agent alongside your own application and connect it with a monitor key — no calls to write by hand.
Getting metrics from an app running on your own infrastructure into NevTan doesn't mean writing any networking code. Install the NevTan monitoring agent next to your app, paste in the monitor key you created, and the agent takes care of reporting from there.
Add the agent to a Java / Spring Boot app
- 1Create a monitor keyIf you haven't already, create one from the Monitor Keys page — see Monitor keys.
- 2Add the agent as a dependencyThe agent is published on JitPack, so add that repository alongside the dependency itself. These are the same two blocks the console shows you after you click Connect an app.
- 3Paste in your monitor keyAdd the key to your app's own configuration file, along with a name for the service and the ingest endpoint the agent reports to.
- 4Deploying in Docker? Use the environment variables insteadDotted property names don't bind as environment variables — an agent configured that way starts but never reports. In a container, set the UPPER_SNAKE_CASE equivalents.
- 5Start your appOn startup, the agent begins reporting JVM and system metrics — heap, GC, threads, CPU, memory — automatically. There is nothing further to trigger from your side. It logs one line confirming it is running, which you can check with
docker logs <container> | grep nevtan-monitor.
Configuration values
| Parameter | Type | Description |
|---|---|---|
nevtan.monitor.api-keyrequired | string | The monitor key you created in the console — this is how the agent identifies your app. As an environment variable: NEVTAN_MONITOR_API_KEY. |
nevtan.monitor.service-namerequired | string | The name this app reports under. As an environment variable: NEVTAN_MONITOR_SERVICE_NAME. |
nevtan.monitor.endpointrequired | string | The ingest URL the agent posts to. As an environment variable: NEVTAN_MONITOR_ENDPOINT. |
The agent handles reporting for you
You never send metrics to NevTan yourself — the agent is the only thing that talks to NevTan on your app's behalf. If you don't see data, double-check the key value and that the agent dependency actually shipped with your running build.
Note
Once the agent starts reporting, the key flips to up in Monitor keys and its history appears in Key monitoring.