Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

DITAS - VDC Logging Agent

The VDC Logging agent is a small software service to enable a VDC to transmit metrics and instrumentation information to the DITAS platform. The agent offers a rest interface to each VDC, which enables access to elastic search and Zipkin without requiring the VDC to included specific dependencies for these services. The agent is intended to run in the same container as the VDC and is compiled with static libraries, allowing it to be deployed in any Unix-like environment.

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.


To install the go lang tools go to: Go Getting Started


For installation you have two options, building and running it on your local machine or using the docker approach.

For local testing and building for that you can follow the following steps:

install dependencies (only needs to be done once):

compile CGO_ENABLED=0 GOOS=linux go build -a --installsuffix cgo --ldflags="-w -s -X main.Build=$(git rev-parse --short HEAD)" -o log-agnt

to run locally: ./log-agnt

For the docker approach, you can use the provided dockerfile to build a running artifact as a Docker container.

build the docker container: docker build -t ditas/logging-agent -f Dockerfile.artifact .

Attach the docker container to a VDC or other microservice like component: docker run -v ./logging.json:/opt/blueprint/logging.json --pid=container:<APPID> -p 8484:8484 ditas/logging-agent

Here <APPID> must be the container ID of the application you want to observe. The port at 8484 is used for the logging rest interface and only needs to be exposed if you plan on logging data of external services outside the attached container. Also, refer to the Configuration section for information about the logging.json-config file.

Running the tests

For testing you can use: go test ./...

For that make sure you have an elastic search running locally at the default port.


To configure the agent, you can specify the following values in a JSON file:


  • VDCName => the Name used to store the information under
  • Endpoint => the address used as the service address in zipkin
  • Port => port of the agent
  • verbose => boolean to indicate if the agent should use verbose logging (recommended for debugging)
  • waitTime => the duration for which the server gracefully wait for existing connections to finish in secounds


  • ElasticSearchURL => The URL that all aggregated data is sent to
  • ElasticBasicAuth => boolean to indicate if authentication for the elastic is required
  • ElasticUser => username for the elasticsearch
  • ElasticPassword => password for the elasticsearch
  • IgnoreElastic => boolean which disables the sending of data to the elastic search (use only for testing)


  • ZipkinEndpoint => the address of the zipkin collector
  • tracing => boolean that indicates if tracing should be enabled

An example file could look like this:

    "waitTime": 10,
    "ElasticBasicAuth": true,
    "ElasticUser": "user",
    "ElasticPassword": "123456",
    "IgnoreElastic": false,
    "ZipkinEndpoint": "",
    "tracing": true


Alternatively, users can use flags with the same name to configure the agent.


The command line options are:

  • -port port that the agent should listen on
  • -zipkin Zipkin endpoint
  • -vdc VDC name that this agent is paired with (used as the elastic search index)
  • -elastic elastic search address
  • -wait the duration for which the server gracefully wait for existing connections in seconds


This agent offers a logging API that can be used by attached applications to forward important information to the DITAS monitoring system.

An excerpt of the version 1.0.0 API can be found here.

Built With


We use SemVer for versioning. For the versions available, see the tags on this repository.


This project is licensed under the Apache 2.0 - see the file for details.


This is being developed for the DITAS Project