Custom metrics visualization with Grafana and InfluxDB

If you need a solution for querying and visualizing time series and metrics probably your first choice will be Grafana. Grafana is a visualization dashboard and it can collect data from some different databases like MySQL, Elasticsearch and InfluxDB. At present it is becoming very popular to integrate with InfluxDB as a data source. This is a solution specifically designed for storing real-time metrics and events and is very fast and scalable for time-based data. Today, I’m going to show an example Spring Boot application of metrics visualization based on Grafana, InfluxDB and alerts using Slack communicator.

Spring Boot Actuator exposes some endpoint useful for monitoring and interacting with application. It also includes a metrics service with gauge and counter support. Gauge records a single value, counter records incremented or decremented value in all previous steps. The full list of basic metrics is available in Spring Boot documentation here and these are for example free memory, heap usage, datasource pool usage or thread information. We can also define our own custom metrics. To allow exporting such values into InfluxDB we need to declare bean @ExportMetricWriter. Spring Boot has not build-in metrics exporter for InfluxDB, so we have add influxdb-java library into pom.xml dependencies and define connection properties.

	GaugeWriter influxMetricsWriter() {
		InfluxDB influxDB = InfluxDBFactory.connect("", "root", "root");
		String dbName = "grafana";
		influxDB.enableBatch(10, 1000, TimeUnit.MILLISECONDS);

		return new GaugeWriter() {

			public void set(Metric<?> value) {
				Point point = Point.measurement(value.getName()).time(value.getTimestamp().getTime(), TimeUnit.MILLISECONDS)
						.addField("value", value.getValue()).build();
				influxDB.write(point);"write(" + value.getName() + "): " + value.getValue());

The metrics should be read from Actuator endpoint, so we should declare MetricsEndpointMetricReader bean.

	public MetricsEndpointMetricReader metricsEndpointMetricReader(final MetricsEndpoint metricsEndpoint) {
		return new MetricsEndpointMetricReader(metricsEndpoint);

We can customize exporting process by declaring properties inside application.yml file. In the code fragment below there are two parameters: delay-millis which set metrics export interval to 5 seconds and includes, where we can define which metric should be exported.

      delay-millis: 5000
      includes: heap.used,heap.committed,mem,,threads,,datasource.primary.usage,gauge.response.persons,,gauge.response.persons.remove

To easily run Grafana and InfluxDB let’s use docker.

docker run -d --name grafana -p 3000:3000 grafana/grafana
docker run -d --name influxdb -p 8086:8086 influxdb

Grafana is available under default security credentials admin/admin. The first step is to create InfluxDB data source.

Now, we can create our new dashboard and add some graphs. Before it run Spring Boot sample application to export metrics some data into InfluxDB. Grafana has user friendly support for InfluxDB queries, where you can click the entire configuration and have a hint of syntax. Of course there is also a possibility of writing text queries, but not all of query language features are available.


Here’s the picture with my Grafana dashboard for metrics passed in includes property. On the second picture below you can see enlarged graph with average REST methods processing time.



We can always implement our custom service which generates metrics sent to InfluxDB. Spring Boot Actuator provides two classes for that purpose: CounterService and GaugeService. Below, there is example of GaugeService usage, where the random value between 0 and 100 is generated in 100ms intervals.

public class FirstService {

    private final GaugeService gaugeService;

    public FirstService(GaugeService gaugeService) {
        this.gaugeService = gaugeService;

    public void exampleMethod() {
    	Random r = new Random();
    	for (int i = 0; i < 1000000; i++) {
    		this.gaugeService.submit("firstservice", r.nextDouble()*100);
    		try {
			} catch (InterruptedException e) {


The sample bean FirstService is starting after application startup.

public class Start implements ApplicationListener<ContextRefreshedEvent> {

	private FirstService service1;

	public void onApplicationEvent(ContextRefreshedEvent contextRefreshedEvent) {


Now, let’s configure alert notification using Grafana dashboard and Slack. This feature is available from 4.0 version. I’m going to define a threshold for statistics sent by FirstService bean. If you have already created graph for gauge.firstservice (you need to add this metric name into includes property inside application.yml) go to edit section and then to Alert tab. There you can define alerting condition by selecting aggregating function (for example avg, min, max), evaluation interval and threshold value. For my sample visible in the picture below I selected alerting when maximum value is bigger than 95 and conditions should be evaluated in 5 minute intervals.


After creating alert configuration we should define notification channel. There are some interesting supported notification types like email, Hip Chat, webhook or Slack. When configuring Slack notification we need to pass recipient’s address or channel name and incoming webhook URL. Then, add new notification for your alert sent to Slack in Notifications section.


I created dedicated channel #grafana for Grafana notification on my Slack account and attached incoming webhook to this channel by searching it in Channel Settings -> Add app or integration.


Finally, run my sample application and don’t forget to logout from Grafana Dashboard in case you would like to receive alert on Slack.


Author: Piotr Mińkowski

IT Architect, Java Software Developer

3 thoughts on “Custom metrics visualization with Grafana and InfluxDB”

  1. While following the “first step is to create InfluxDB data source.” I got this message – “Could not find the specified database name”. Would like to know how to go ahead with creating database and when I am trying to access localhost:8086 (which is url for influxDB) I am getting 404 but when using
    $ curl -G ‘http://localhost:8086/query’ –data-urlencode “db=grafana” –data-urlencode “q=SELECT * FROM points” -vvvv

    * Trying ::1…
    * Connected to localhost (::1) port 8086 (#0)
    > GET /query?db=grafana&q=SELECT%20%2A%20FROM%20points HTTP/1.1
    > Host: localhost:8086
    > User-Agent: curl/7.43.0
    > Accept: */*
    < HTTP/1.1 200 OK
    < Connection: close
    < Content-Type: application/json
    < Request-Id: 8b854cd0-730a-11e7-800a-000000000000
    < X-Influxdb-Version: 1.3.1
    < Date: Thu, 27 Jul 2017 20:31:18 GMT
    < Transfer-Encoding: chunked
    {"results":[{"statement_id":0,"error":"database not found: grafana"}]}
    * Closing connection 0


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s