--- title: "Apache Mesos integration | Grafana Cloud documentation" description: "Learn about Apache Mesos Grafana Cloud integration." --- > For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt). # Apache Mesos integration for Grafana Cloud Apache Mesos is an open-source distributed systems kernel that acts as a platform for managing and orchestrating computing resources across clusters of machines. Apache Mesos integration for Grafana cloud allows users to monitor masters events queue, registrar state, allocator usage as well as disk, memory and logs for both the master and agent targets in an overview dashboard. This integration supports Apache Mesos 1.4.x+ This integration supports the [Prometheus Mesos Exporter](https://github.com/mesos/mesos_exporter) v1.1.2 This integration includes 5 useful alerts and 1 pre-built dashboard to help monitor and visualize Apache Mesos metrics and logs. ## Before you begin In order for the integration to work properly, you must enable logs and set up the [Prometheus Mesos Exporter](https://github.com/mesos/mesos_exporter) on your primary host. In a production environment, Apache Mesos master and agent node are ran separately for better [resource management](https://mesos.apache.org/documentation/latest/#resource-management), [availability](https://mesos.apache.org/documentation/latest/high-availability/) and [fault tolerance](https://mesos.apache.org/documentation/latest/agent-recovery/). 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](https://mesos.apache.org/documentation/latest/configuration/master-and-agent/#logging-options) 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](https://github.com/mesos/mesos_exporter) 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 Alloy process with `mesos_exporter -slave http://localhost:5051`. For more information on how to configure the Prometheus exporter, please refer to [Prometheus configuration documentation](https://github.com/mesos/mesos_exporter#prometheus-configuration). To validate that the Prometheus exporter is working correctly, curl the master Prometheus metrics endpoint on the port `9105`: sh ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```sh 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 Alloy 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 Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```alloy discovery.relabel "metrics_integrations_integrations_apache_mesos" { targets = [{ __address__ = ":", }] rule { target_label = "mesos_cluster" replacement = "" } 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](/docs/alloy/latest/reference/components/discovery.relabel/) component to discover your Apache Mesos Prometheus endpoint and apply appropriate labels, followed by a [prometheus.scrape](/docs/alloy/latest/reference/components/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 Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```alloy local.file_match "logs_integrations_integrations_apache_mesos" { path_targets = [{ __address__ = "localhost", __path__ = "", instance = constants.hostname, job = "integrations/apache-mesos", mesos_cluster = "", }] } 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](/docs/alloy/latest/reference/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](/docs/grafana-cloud/data-configuration/integrations/integration-reference/integration-apache-mesos/#enable-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](/docs/alloy/latest/reference/components/loki.source.file) sends logs to Loki. #### windows Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```alloy local.file_match "logs_integrations_integrations_apache_mesos" { path_targets = [{ __address__ = "localhost", __path__ = "", instance = constants.hostname, job = "integrations/apache-mesos", mesos_cluster = "", }] } 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](/docs/alloy/latest/reference/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](/docs/grafana-cloud/data-configuration/integrations/integration-reference/integration-apache-mesos/#enable-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](/docs/alloy/latest/reference/components/loki.source.file) sends logs to Loki. ## Kubernetes instructions Instructions for Kubernetes ### Before you begin with Kubernetes **Please note**: These instructions assume the use of the [Kubernetes Monitoring Helm chart](https://github.com/grafana/k8s-monitoring-helm) In order for the integration to work properly, you must enable logs and set up the [Prometheus Mesos Exporter](https://github.com/mesos/mesos_exporter) on your primary host. In a production environment, Apache Mesos master and agent node are ran separately for better [resource management](https://mesos.apache.org/documentation/latest/#resource-management), [availability](https://mesos.apache.org/documentation/latest/high-availability/) and [fault tolerance](https://mesos.apache.org/documentation/latest/agent-recovery/). 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](https://mesos.apache.org/documentation/latest/configuration/master-and-agent/#logging-options) 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](https://github.com/mesos/mesos_exporter) 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](https://github.com/mesos/mesos_exporter#prometheus-configuration). To validate that the Prometheus exporter is working correctly, curl the master Prometheus metrics endpoint on the port `9105`: sh ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```sh curl http://localhost:9105/metrics ``` ### Configuration snippets for Kubernetes Helm chart The following snippets provide examples to guide you through the configuration process. To scrape your Apache Mesos instances, **manually** modify your Kubernetes Monitoring Helm chart with these configuration snippets. Replace any values between the angle brackets `<>` in the provided snippets with your desired configuration values. #### Metrics snippets Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```alloy alloy-metrics: extraConfig: |- discovery.kubernetes "apache_mesos" { role = "endpoints" selectors { role = "service" field = "metadata.name=" } } discovery.relabel "apache_mesos" { targets = discovery.kubernetes.apache_mesos.targets rule { source_labels = ["__meta_kubernetes_endpoint_port_name"] regex = "" action = "keep" } rule { replacement = "" target_label = "mesos_cluster" } } prometheus.scrape "integrations_mesos_statsd_exporter" { targets = discovery.relabel.apache_mesos.output job_name = "integrations/apache-mesos" forward_to = [prometheus.remote_write.grafana_cloud_metrics.receiver] } ``` #### Logs snippets Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```alloy podLogs: extraDiscoveryRules: |- rule { source_labels = ["__meta_kubernetes_namespace", "__meta_kubernetes_pod_name", "__meta_kubernetes_pod_container_name"] separator = ":" regex = "(::)" replacement = "apache_mesos" target_label = "integration" } rule { source_labels = ["integration"] regex = "apache_mesos" replacement = "master" target_label = "log_type" } rule { source_labels = ["__meta_kubernetes_namespace", "__meta_kubernetes_pod_name", "__meta_kubernetes_pod_container_name"] separator = ":" regex = "(::)" replacement = "apache_mesos" target_label = "integration" } rule { source_labels = ["integration", "log_type"] separator = ":" regex = "apache_mesos:" replacement = "agent" target_label = "log_type" } rule { source_labels = ["integration", "__meta_kubernetes_node_name"] separator = ":" regex = "apache_mesos:(.*)" target_label = "node" } rule { source_labels = ["integration"] regex = "apache_mesos" replacement = "" target_label = "mesos_cluster" } rule { source_labels = ["integration"] regex = "apache_mesos" replacement = "integrations/mesos" target_label = "job" } ``` ## Dashboards The Apache Mesos integration installs the following dashboards in your Grafana Cloud instance to help monitor your system. - Apache Mesos overview **Apache Mesos overview dashboard part 1** **Apache Mesos overview dashboard part 2** ## Alerts The Apache Mesos integration includes the following useful alerts: Expand table | Alert | Description | |-----------------------------|-------------------------------------------------------------------| | ApacheMesosHighMemoryUsage | Warning: There is a high memory usage for the cluster. | | ApacheMesosHighDiskUsage | Critical: There is a high disk usage for the cluster. | | ApacheMesosUnreachableTasks | Warning: There are an unusually high number of unreachable tasks. | | ApacheMesosNoLeaderElected | Critical: There is currently no cluster coordinator. | | ApacheMesosInactiveAgents | Warning: There are currently inactive agent clients. | ## Metrics The most important metrics provided by the Apache Mesos integration, which are used on the pre-built dashboard and Prometheus alerts, are as follows: - mesos\_exporter\_build\_info - mesos\_master\_allocation\_run\_latency\_ms - mesos\_master\_allocation\_run\_ms - mesos\_master\_allocation\_run\_ms\_count - mesos\_master\_cpus - mesos\_master\_disk - mesos\_master\_elected - mesos\_master\_event\_queue\_dispatches - mesos\_master\_event\_queue\_length - mesos\_master\_gpus - mesos\_master\_mem - mesos\_master\_messages - mesos\_master\_slaves\_state - mesos\_master\_task\_states\_current - mesos\_master\_uptime\_seconds - mesos\_registrar\_log\_recovered - mesos\_registrar\_state\_fetch\_ms - mesos\_registrar\_state\_store\_ms - mesos\_slave\_disk\_bytes - mesos\_slave\_disk\_used\_bytes - mesos\_slave\_mem\_bytes - mesos\_slave\_mem\_used\_bytes - up ## Changelog md ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```md # 1.0.0 - July 2024 * Add Kubernetes as a supported platform using Grafana Alloy # 0.0.3 - September 2023 * New Filter Metrics option for configuring the Grafana Agent, which saves on metrics cost by dropping any metric not used by this integration. Beware that anything custom built using metrics that are not on the snippet will stop working. * New hostname relabel option, which applies the instance name you write on the text box to the Grafana Agent configuration snippets, making it easier and less error prone to configure this mandatory label. # 0.0.2 - August 2023 * Add regex filter for logs datasource # 0.0.1 - June 2023 * Initial release ``` ## Cost By connecting your Apache Mesos instance to Grafana Cloud, you might incur charges. To view information on the number of active series that your Grafana Cloud account uses for metrics included in each Cloud tier, see [Active series and dpm usage](/docs/grafana-cloud/fundamentals/active-series-and-dpm/) and [Cloud tier pricing](/products/cloud/pricing/).