Logs analysis with OVH Logs Data Platform

OVH offers a service called “Logs Data Platform” which helps you centralize and analyze your logs.

I see two main benefits of using this service:

  1. It’s a managed service (SaaS)
  2. It’s cheap

The offering starts at 1€ per month for 1GB of logs with one stream of logs and one dashboard. The data retention is of 45 days.

It also allows me to set up multiple users and define more fine-grained access rules even though I did not test the feature.

The service allows interacting with your logs using Graylog or Elastisearch.

So I decided to give it a try. I will store and analyze the logs of Inkzone, a website I am currently working on.

About Graylog and GELF format

Graylog is a tool that centralizes your logs in one place and make it easier to browse and analyze them.

The more applications you have the more benefits you’ll get from this kind of tool. The more you have, the more log files you also have to manage with rotation and retention policy.

Greylog uses a log format called GELF (Graylog Extended Lenght Format). GELF differs from other log formats (like syslog) by being a structured logging format with custom typed fields. This makes it better suited for indexing and analysis than other non structured formats.

Send Docker container logs to Graylog

Docker has a native gelf log driver. If you use Docker to deploy your applications and print your logs in the standard output to print your logs you can directly send your logs to graylog by changing the log driver of your containers.

In order to proceed you will need to know:

  • The endpoint to collect GELF logs over UDP (udp://gra2.logs.ovh.com:2202 for me)
  • The token for your stream

Then, run the docker container with the following configuration:

docker run \
  -e X-OVH-TOKEN="7982bbc4-9a66-4426-9de3-33d6eb201ed6" \
  --log-driver gelf \
  --log-opt gelf-address=udp://gra2.logs.ovh.com:2202 \
  --log-opt env=X-OVH-TOKEN \
  -d busybox

Replace 7982bbc4-9a66-4426-9de3-33d6eb201ed6 by your actual Stream token.

--log-opt env=X-OVH-TOKEN for the gelf log driver will put the specified environment variable as a custom field in the GELF message (prefixed by an underscore _). That’s how OVH can accept and properly route the incoming logs.

It works, however, the main drawback is that the logs will be made from the Docker perspective. The reported log levels are the ones from Docker, not from the java app. Docker will only consider for log levels the standard and error outputs, so you will not have the same granularity as the java logs (DEBUG, INFO, WARN, ERROR, etc.) without doing intermediate processing.

If you want richer logs there are two possible approaches:

  1. Configure and use an Extractor in graylog
  2. Send logs from the Java logging framework of your choice (logback in my case)

Send logback logs to Graylog

From logback you can send the logs to Greylogs by adding a new Appender:

<?xml version="1.0" encoding="UTF-8"?>
<configuration debug="true">

  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
    <layout class="ch.qos.logback.classic.PatternLayout">
        %level %logger - %msg%n

  <appender name="GELF" class="de.siegmar.logbackgelf.GelfUdpAppender">
    <layout class="de.siegmar.logbackgelf.GelfLayout">

  <root level="INFO">
    <appender-ref ref="STDOUT" />
    <appender-ref ref="GELF" />


Replace 7982bbc4-9a66-4426-9de3-33d6eb201ed6 by your actual Stream token.

You’ll need to add the following dependency to you project: compile 'de.siegmar:logback-gelf:1.0.4'

There is logback appender biz.paluch.logging:logstash-gelf that is quite popular, but I did not manage to make it work. So I went for de.siegmar:logback-gelf instead.