Skip to content

Marathon Integration

Infrastructure Integration

Instructions

Follow the installation guide below for your given collector environment.

During installation, use the configuration file below as reference.

After installation, the infrastructure datasources in the table below will be available in the AOC.

Installation Guide

Installing this integration consists of creating a yaml file in the filesystem of your collectors. Click below for instructions on how to do so for your given collectors environment.

Docker

Kubernetes

Mesos-Marathon

Debian

Ubuntu

RHEL/CentOS

Configuration File

Edit marathon.yaml to configure the agent. Please refer marathon.yaml for all available configuration options.

    init_config:
      - default_timeout: 5

    instances:
      - url: "https://server:port"
        acs_url: the base ACS endpoint url if an ACS token is required to access the marathon API
        acs_url: https://server:port

Infrastructure Datasources

Datasource Available Aggregations Unit Description
marathon.apps avg max min sum Number of defined apps
marathon.backoffFactor avg max min sum Backoff time multiplication factor for each consecutive failed task launch
marathon.backoffSeconds avg max min sum second Task backoff period
marathon.cpus avg max min sum Number of CPU's this application needs per instance
marathon.disk avg max min sum mebibyte Disk that is needed for the application
marathon.instances avg max min sum Number of instances of this application to start
marathon.mem avg max min sum mebibyte Memory that is needed for the application per instance
marathon.tasksRunning avg max min sum task Number of tasks running
marathon.tasksStaged avg max min sum task Number of tasks staged to run
marathon.queue.size avg max min sum Number of apps waiting for deployment