Docs » Available host and application monitors » Configure application receivers for orchestration » Mesos Marathon

Mesos Marathon ๐Ÿ”—

Description ๐Ÿ”—

The Splunk Distribution of OpenTelemetry Collector provides this integration as the Mesos Marathon monitor type by using the Smart Agent Receiver.

Use this integration to monitor a Mesos Marathon instance using the Marathon Python plugin.

This monitor is available on Kubernetes, Linux, and Windows.

Benefits ๐Ÿ”—

After you configure the integration, you can access these features:

Installation ๐Ÿ”—

Follow these steps to deploy this integration:

  1. Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:

  2. Configure the monitor, as described in the Configuration section.

  3. Restart the Splunk Distribution of OpenTelemetry Collector.

Configuration ๐Ÿ”—

This monitor type is available in the Smart Agent Receiver, which is part of the Splunk Distribution of OpenTelemetry Collector. You can use existing Smart Agent monitors as OpenTelemetry Collector metric receivers with the Smart Agent Receiver.

This monitor type requires a properly configured environment on your system in which youโ€™ve installed a functional Smart Agent release bundle. The Collector provides this bundle in the installation paths for x86_64/amd64.

To activate this monitor type in the Collector, add the following lines to your configuration (YAML) file:

receivers:
  smartagent/marathon:
    type: collectd/marathon
    ... # Additional config

To complete the integration, include the Smart Agent receiver using this monitor in a metrics pipeline. To do this, add the receiver to the service > pipelines > metrics > receivers section of your configuration file.

service:
  pipelines:
    metrics:
      receivers: [smartagent/marathon]

See configuration examples for specific use cases that show how the Splunk Distribution of OpenTelemetry Collector can integrate and complement existing environments.

Configuration settings ๐Ÿ”—

The following table shows the configuration options for the Mesos Marathon monitor:

Option

Required

Type

Description

pythonBinary

no

string

Path to a python binary that should be used to execute the Python code. If not set, a built-in runtime will be used. Can include arguments to the binary as well.

host

yes

string

Host of the exporter

port

yes

integer

Port of the exporter

username

no

string

Username used to authenticate with Marathon.

password

no

string

Password used to authenticate with Marathon.

scheme

no

string

Set to either http or https. (default: http)

dcosAuthURL

no

string

The dcos authentication URL that the plugin uses to get authentication tokens from. Set scheme to โ€œhttpsโ€ if operating DC/OS in strict mode and dcosAuthURL to โ€œhttps://leader.mesos/acs/api/v1/auth/loginโ€ (which is the default DNS entry provided by DC/OS)

The following is a sample YAML configuration:

monitors:
  - type: collectd/marathon
    host: 127.0.0.1
    port: 8080
    scheme: http

The following is a sample YAML configuration for DC/OS:

monitors:
  - type: collectd/marathon
    host: 127.0.0.1
    port: 8080
    scheme: https
    dcosAuthURL: https://leader.mesos/acs/api/v1/auth/login

Metrics ๐Ÿ”—

The following metrics are available for this integration:

Get help ๐Ÿ”—

If you are not able to see your data in Splunk Observability Cloud, try these tips:

To learn about even more support options, see Splunk Customer Success.