Apache Mesos integration for Grafana Cloud

Before you begin

In order for the integration to work properly, you must enable logs and set up the Prometheus Mesos Exporter on your primary host. In a production environment, Apache Mesos master and agent node are ran separately for better resource management, availability and fault tolerance. Each master or agent node has their own log path and requires a prometheus exporter installation.

Enable logs for Apache Mesos

Users must enable Apache Mesos Logs in order for log panels on the dashboard to populate. Logs are added to either the Mesos master or agent node by specifying the log directory using --log_dir=. This path will also differ depending on if you are running Linux or Windows but is required so that Promtail can ingest the logs.

Run the Mesos master with the following flags:
--log_dir=/var/log/mesos/master/ on Linux masters
–-log_dir=C:\Program Files\mesos\master\ on Windows masters

Run the Mesos agent with the following flags:
--log_dir=/var/log/mesos/agent/ on Linux agents
–-log_dir=C:\Program Files\mesos\agent\ on Windows agents

Set up Prometheus Exporter for Apache Mesos

The Prometheus Mesos Exporter v1.1.2 must be setup with a Prometheus configuration file specifying a master or agent node. Run the Mesos exporter master process with mesos_exporter -master http://localhost:5050 and run the Mesos exporter for the agent process with mesos_exporter -slave http://localhost:5051. For more information on how to configure the Prometheus exporter, please refer to Prometheus configuration documentation.

To validate that the Prometheus exporter is working correctly, curl the master Prometheus metrics endpoint on the port 9105:

sh Copy

curl http://localhost:9105/metrics

Install Apache Mesos integration for Grafana Cloud

1. In your Grafana Cloud stack, click Connections in the left-hand menu.
2. Find Apache Mesos and click its tile to open the integration.
3. Review the prerequisites in the Configuration Details tab and set up Grafana Agent to send Apache Mesos metrics and logs to your Grafana Cloud instance.
4. Click Install to add this integration’s pre-built dashboard and alerts to your Grafana Cloud instance, and you can start monitoring your Apache Mesos setup.

Configuration snippets for Grafana Alloy

Advanced mode

The following snippets provide examples to guide you through the configuration process.

To instruct Grafana Alloy to scrape your Apache Mesos instances, manually copy and append the snippets to your alloy configuration file, then follow subsequent instructions.

Advanced metrics snippets

river Copy

discovery.relabel "metrics_integrations_integrations_apache_mesos" {
	targets = [{
		__address__ = "<node-name>:<node-exporter-port>",
	}]

	rule {
		target_label = "mesos_cluster"
		replacement  = "<your-cluster-name>"
	}

	rule {
		target_label = "instance"
		replacement  = constants.hostname
	}
}

prometheus.scrape "metrics_integrations_integrations_apache_mesos" {
	targets    = discovery.relabel.metrics_integrations_integrations_apache_mesos.output
	forward_to = [prometheus.remote_write.metrics_service.receiver]
	job_name   = "integrations/apache-mesos"
}

To monitor your Apache Mesos instance, you must use a discovery.relabel component to discover your Apache Mesos Prometheus endpoint and apply appropriate labels, followed by a prometheus.scrape component to scrape it.

Configure the following properties within each discovery.relabel component:

• __address__: The address to your Apache Mesos Prometheus metrics endpoint.
• instance label: constants.hostname sets the instance label to your Grafana Alloy server hostname. If that is not suitable, change it to a value uniquely identifies this Apache Mesos instance. Make sure this label value is the same for all telemetry data collected for this instance.
• mesos_cluster: The mesos_cluster label to group your Apache Mesos instances within a cluster. Set the same value for all nodes within your cluster.

If you have multiple Apache Mesos servers to scrape, configure one discovery.relabel for each and scrape them by including each under targets within the prometheus.scrape component.

Advanced logs snippets

linux

river Copy

local.file_match "logs_integrations_integrations_apache_mesos" {
	path_targets = [{
		__address__   = "localhost",
		__path__      = "<mesos-node-log-dir>",
		instance      = constants.hostname,
		job           = "integrations/apache-mesos",
		mesos_cluster = "<mesos-cluster-name>",
	}]
}

loki.source.file "logs_integrations_integrations_apache_mesos" {
	targets    = local.file_match.logs_integrations_integrations_apache_mesos.targets
	forward_to = [loki.write.grafana_cloud_loki.receiver]
}

To monitor your Apache Mesos instance logs, you will use a combination of the following components:

• local.file_match defines where to find the log file to be scraped. Change the following properties according to your environment:

  • __address__: The Apache Mesos instance address
  • __path__: The path to the log file. It must be the log dir specified in the --log_dir= depending on your node and OS as instructed when enabling logs for Apache Mesos whose default values would be either:
    1. /var/log/mesos/master/ for a master node on Linux
    2. C:\Program Files\mesos\master\ for a master node on Windows
    3. /var/log/mesos/agent/ for an agent node on Linux
    4. C:\Program Files\mesos\agent\ for an agent node on Windows
  • instance label: constants.hostname sets the instance label to your Grafana Alloy server hostname. If that is not suitable, change it to a value uniquely identifies this Apache Mesos instance. Make sure this label value is the same for all telemetry data collected for this instance.
  • mesos_cluster: The mesos_cluster label to group your Apache Mesos instances within a cluster. Set the same value for all nodes within your cluster.

• loki.source.file sends logs to Loki.

windows

river Copy

local.file_match "logs_integrations_integrations_apache_mesos" {
	path_targets = [{
		__address__   = "localhost",
		__path__      = "<mesos-node-log-dir>",
		instance      = constants.hostname,
		job           = "integrations/apache-mesos",
		mesos_cluster = "<mesos-cluster-name>",
	}]
}

loki.source.file "logs_integrations_integrations_apache_mesos" {
	targets    = local.file_match.logs_integrations_integrations_apache_mesos.targets
	forward_to = [loki.write.grafana_cloud_loki.receiver]
}

To monitor your Apache Mesos instance logs, you will use a combination of the following components:

• local.file_match defines where to find the log file to be scraped. Change the following properties according to your environment:

  • __address__: The Apache Mesos instance address
  • __path__: The path to the log file. It must be the log dir specified in the --log_dir= depending on your node and OS as instructed when enabling logs for Apache Mesos whose default values would be either:
    1. /var/log/mesos/master/ for a master node on Linux
    2. C:\Program Files\mesos\master\ for a master node on Windows
    3. /var/log/mesos/agent/ for an agent node on Linux
    4. C:\Program Files\mesos\agent\ for an agent node on Windows
  • instance label: constants.hostname sets the instance label to your Grafana Alloy server hostname. If that is not suitable, change it to a value uniquely identifies this Apache Mesos instance. Make sure this label value is the same for all telemetry data collected for this instance.
  • mesos_cluster: The mesos_cluster label to group your Apache Mesos instances within a cluster. Set the same value for all nodes within your cluster.

• loki.source.file sends logs to Loki.

Before you begin

In order for the integration to work properly, you must enable logs and set up the Prometheus Mesos Exporter on your primary host. In a production environment, Apache Mesos master and agent node are ran separately for better resource management, availability and fault tolerance. Each master or agent node has their own log path and requires a prometheus exporter installation.

Enable logs for Apache Mesos

Users must enable Apache Mesos Logs in order for log panels on the dashboard to populate. Logs are added to either the Mesos master or agent node by specifying the log directory using --log_dir=. This path will also differ depending on if you are running Linux or Windows but is required so that Promtail can ingest the logs.

Run the Mesos master with the following flags:
--log_dir=/var/log/mesos/master/ on Linux masters
–-log_dir=C:\Program Files\mesos\master\ on Windows masters

Run the Mesos agent with the following flags:
--log_dir=/var/log/mesos/agent/ on Linux agents
–-log_dir=C:\Program Files\mesos\agent\ on Windows agents

Set up Prometheus Exporter for Apache Mesos

The Prometheus Mesos Exporter v1.1.2 must be setup with a Prometheus configuration file specifying a master or agent node. Run the Mesos exporter master process with mesos_exporter -master http://localhost:5050 and run the Mesos exporter for the agent process with mesos_exporter -slave http://localhost:5051. For more information on how to configure the Prometheus exporter, please refer to Prometheus configuration documentation.

To validate that the Prometheus exporter is working correctly, curl the master Prometheus metrics endpoint on the port 9105:

sh Copy

curl http://localhost:9105/metrics

Install Apache Mesos integration for Grafana Cloud

1. In your Grafana Cloud stack, click Connections in the left-hand menu.
2. Find Apache Mesos and click its tile to open the integration.
3. Review the prerequisites in the Configuration Details tab and set up Grafana Agent to send Apache Mesos metrics and logs to your Grafana Cloud instance.
4. Click Install to add this integration’s pre-built dashboard and alerts to your Grafana Cloud instance, and you can start monitoring your Apache Mesos setup.

Post-install configuration for the Apache Mesos integration

After enabling Apache Mesos logs and the Prometheus Mesos Exporter, instruct the Grafana Agent to scrape your Apache Mesos cluster.

Make sure to change targets in the snippet according to your environment master or agent name. The default port for Apache Mesos master targets is 9105.

If you want to show logs and metrics signals correlated in your dashboards as a single pane of glass, ensure the following:

• job and mesos_cluster label values must match for the Apache Mesos metrics and logs scrape config in your agent configuration file.
• job must be set to integrations/apache-mesos Please replace the default hostname for the master or agent Mesos node name and port according to your environment manually.
• mesos_cluster must be the value that identifies the Apache Mesos cluster master or agent it belongs to.
• mesos-node-log-dir must be the log dir specified in the --log_dir= depending on your node and OS as instructed when enabling logs for Apache Mesos whose default values would be either:
  1. /var/log/mesos/master/ for a master node on Linux
  2. C:\Program Files\mesos\master\ for a master node on Windows
  3. /var/log/mesos/agent/ for an agent node on Linux
  4. C:\Program Files\mesos\agent\ for an agent node on Windows

Configuration snippets for Grafana Agent

Below metrics.configs.scrape_configs, insert the following lines and change the URLs according to your environment:

yaml Copy

    - job_name: integrations/apache-mesos
      metrics_path: "/metrics"
      static_configs:
        # node refers to either the master or agent
        - targets: ['<node-name>:<node-exporter-port>']
      relabel_configs:
        - target_label: mesos_cluster
          replacement: '<your-cluster-name>'
        - target_label: instance
          replacement: '<your-instance-name>'

Below logs.configs.scrape_configs, insert the following lines according to your environment.

yaml Copy

    - job_name: integrations/apache-mesos
      static_configs:
        - targets: [localhost]
          labels:
            job: integrations/apache-mesos
            instance: '<your-instance-name>'
            mesos_cluster: '<mesos-cluster-name>'
            # See Apache Mesos pre instructions for node and OS specific log directory
            # https://grafana.com/docs/grafana-cloud/data-configuration/integrations/integration-reference/integration-apache-mesos/#enable-logs-for-apache-mesos
            __path__: '<mesos-node-log-dir>'

Full example configuration for Grafana Agent

Refer to the following Grafana Agent configuration for a complete example that contains all the snippets used for the Apache Mesos integration. This example also includes metrics that are sent to monitor your Grafana Agent instance.

yaml Copy

integrations:
  prometheus_remote_write:
  - basic_auth:
      password: <your_prom_pass>
      username: <your_prom_user>
    url: <your_prom_url>
  agent:
    enabled: true
    relabel_configs:
    - action: replace
      source_labels:
      - agent_hostname
      target_label: instance
    - action: replace
      target_label: job
      replacement: "integrations/agent-check"
    metric_relabel_configs:
    - action: keep
      regex: (prometheus_target_sync_length_seconds_sum|prometheus_target_scrapes_.*|prometheus_target_interval.*|prometheus_sd_discovered_targets|agent_build.*|agent_wal_samples_appended_total|process_start_time_seconds)
      source_labels:
      - __name__
  # Add here any snippet that belongs to the `integrations` section.
  # For a correct indentation, paste snippets copied from Grafana Cloud at the beginning of the line.
logs:
  configs:
  - clients:
    - basic_auth:
        password: <your_loki_pass>
        username: <your_loki_user>
      url: <your_loki_url>
    name: integrations
    positions:
      filename: /tmp/positions.yaml
    scrape_configs:
      # Add here any snippet that belongs to the `logs.configs.scrape_configs` section.
      # For a correct indentation, paste snippets copied from Grafana Cloud at the beginning of the line.
    - job_name: integrations/apache-mesos
      static_configs:
        - targets: [localhost]
          labels:
            job: integrations/apache-mesos
            instance: '<your-instance-name>'
            mesos_cluster: '<mesos-cluster-name>'
            # See Apache Mesos pre instructions for node and OS specific log directory
            # https://grafana.com/docs/grafana-cloud/data-configuration/integrations/integration-reference/integration-apache-mesos/#enable-logs-for-apache-mesos
            __path__: '<mesos-node-log-dir>'
metrics:
  configs:
  - name: integrations
    remote_write:
    - basic_auth:
        password: <your_prom_pass>
        username: <your_prom_user>
      url: <your_prom_url>
    scrape_configs:
      # Add here any snippet that belongs to the `metrics.configs.scrape_configs` section.
      # For a correct indentation, paste snippets copied from Grafana Cloud at the beginning of the line.
    - job_name: integrations/apache-mesos
      metrics_path: "/metrics"
      static_configs:
        # node refers to either the master or agent
        - targets: ['<node-name>:<node-exporter-port>']
      relabel_configs:
        - target_label: mesos_cluster
          replacement: '<your-cluster-name>'
        - target_label: instance
          replacement: '<your-instance-name>'
  global:
    scrape_interval: 60s
  wal_directory: /tmp/grafana-agent-wal