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

Mesos Marathon πŸ”—

The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the Mesos Marathon monitor type to monitor a Mesos Marathon instance using the Marathon Python plugin.

This integration is only available on Kubernetes and Linux.

Benefits πŸ”—

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

  • View metrics. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. For information about dashboards, see View dashboards in Observability Cloud.

  • View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Splunk Infrastructure Monitoring navigators.

  • Access the Metric Finder and search for metrics sent by the monitor. For information, see Use the Metric Finder.

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 πŸ”—

To use this integration of a Smart Agent monitor with the Collector:

  1. Include the Smart Agent receiver in your configuration file.

  2. Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

Example πŸ”—

To activate this integration, add the following to your Collector configuration:

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

Next, add the monitor to the service.pipelines.metrics.receivers section of your configuration file:

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

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)

Metrics πŸ”—

The following metrics are available for this integration:

Notes πŸ”—

  • Learn more about the available metric types in Observability Cloud.

  • Default metrics are those metrics included in host-based subscriptions in Observability Cloud, such as host, container, or bundled metrics. Custom metrics are not provided by default and might be subject to charges. See more about metric categories.

  • To add additional metrics, see how to configure extraMetrics using the Collector.

Troubleshooting πŸ”—

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.