Stay organized with collections
Save and categorize content based on your preferences.
This guide explains how to configure the legacy Cloud Monitoring agent to
monitor supported third-party applications. Configuration is only possible when
the legacy Monitoring agent is running on Linux. The agent on
Windows monitors IIS and MS SQL applications; however, on these systems the
agent cannot be configured to collect metrics from other third-party
applications.
The Cloud Monitoring Metrics Management page provides information
that can help you control the amount you spend on billable metrics
without affecting observability. The Metrics Management page reports the
following information:
Ingestion volumes for both byte- and sample-based billing, across metric
domains and for individual metrics.
Data about labels and cardinality of metrics.
Number of reads for each metric.
Use of metrics in alerting policies and custom dashboards.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Monitoring third-party applications\n\nThis guide explains how to configure the legacy Cloud Monitoring agent to\nmonitor supported third-party applications. Configuration is only possible when\nthe legacy Monitoring agent is running on Linux. The agent on\nWindows monitors IIS and MS SQL applications; however, on these systems the\nagent cannot be configured to collect metrics from other third-party\napplications.\n\nSee [Agent metrics](/monitoring/api/metrics_agent) for a list of the available\nmetrics from the third-party applications. The configuration files are in the\nMonitoring agent's [GitHub configuration\nrepository](https://github.com/Stackdriver/stackdriver-agent-service-configs).\n\nAfter you have [installed the legacy Monitoring\nagent](/monitoring/agent/monitoring/installation), see the\nfollowing configuration instructions for supported third-party applications:\n\n- [Apache web server](/monitoring/agent/plugins/apache)\n- [JVM Monitoring](/monitoring/agent/plugins/jvm)\n- [Memcached](/monitoring/agent/plugins/memcached)\n- [MySQL](/monitoring/agent/plugins/mysql)\n- [Nginx](/monitoring/agent/plugins/nginx)\n- [Redis](/monitoring/agent/plugins/redis)\n- [StatsD](/monitoring/agent/plugins/statsd)\n\nThe Cloud Monitoring **Metrics Management** page provides information\nthat can help you control the amount you spend on billable metrics\nwithout affecting observability. The **Metrics Management** page reports the\nfollowing information:\n\n- Ingestion volumes for both byte- and sample-based billing, across metric domains and for individual metrics.\n- Data about labels and cardinality of metrics.\n- Number of reads for each metric.\n- Use of metrics in alerting policies and custom dashboards.\n- Rate of metric-write errors.\n\nYou can also use the **Metrics Management** page to\n[exclude unneeded metrics](/monitoring/docs/metrics-management#exclude-metrics),\neliminating the cost of ingesting them.\n\n\nFor more information about the **Metrics Management** page, see\n[View and manage metric usage](/monitoring/docs/metrics-management)."]]