Monitoring · Ingesting metrics

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

1
Create a monitor key
If you haven't already, create one from the Monitor Keys page — see Monitor keys.
2
Add the agent as a dependency
Add the NevTan agent to your project's build file so it's bundled with your app.
xml
```
 
```
3
Paste in your monitor key
Add the key to your app's own configuration file so the agent knows which key identifies it.
properties
```
 
```
4
Start your app
On startup, the agent begins reporting JVM and system metrics — heap, GC, threads, CPU, memory — automatically. There is nothing further to trigger from your side.

Configuration values

Parameter	Type	Description
`nevtan.monitor.key`required	string	The monitor key you created in the console — this is how the agent identifies your app.
`nevtan.monitor.enabled`	boolean	Turns reporting on or off without removing the dependency. Defaults to enabled once a key is set.

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.