| name | aggregating-performance-metrics |
| description | Aggregate and centralize performance metrics from applications, systems, databases, caches, and services. Use when consolidating monitoring data from multiple sources. Trigger with phrases like "aggregate metrics", "centralize monitoring", or "collect performance data". |
| version | 1.0.0 |
| allowed-tools | Read, Write, Bash(prometheus:*), Bash(metrics:*), Bash(monitoring:*), Grep |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| compatible-with | claude-code, codex, openclaw |
| tags | ["performance","database","monitoring"] |
Metrics Aggregator
Aggregate and centralize performance metrics from applications, databases, caches, and infrastructure into Prometheus, StatsD, or CloudWatch with unified naming conventions.
Overview
This skill empowers Claude to streamline performance monitoring by aggregating metrics from diverse systems into a unified view. It simplifies the process of collecting, centralizing, and analyzing performance data, leading to improved insights and faster issue resolution.
How It Works
- Metrics Taxonomy Design: Claude assists in defining a clear and consistent naming convention for metrics across all systems.
- Aggregation Tool Selection: Claude helps select the appropriate metrics aggregation tool (e.g., Prometheus, StatsD, CloudWatch) based on the user's environment and requirements.
- Configuration and Integration: Claude guides the configuration of the chosen aggregation tool and its integration with various data sources.
- Dashboard and Alert Setup: Claude helps set up dashboards for visualizing metrics and defining alerts for critical performance indicators.
When to Use This Skill
This skill activates when you need to:
- Centralize performance metrics from multiple applications and systems.
- Design a consistent metrics naming convention.
- Choose the right metrics aggregation tool for your needs.
- Set up dashboards and alerts for performance monitoring.
Examples
Example 1: Centralizing Application and System Metrics
User request: "Aggregate application and system metrics into Prometheus."
The skill will:
- Guide the user in defining metrics for applications (e.g., request latency, error rates) and systems (e.g., CPU usage, memory utilization).
- Help configure Prometheus to scrape metrics from the application and system endpoints.
Example 2: Setting Up Alerts for Database Performance
User request: "Centralize database metrics and set up alerts for slow queries."
The skill will:
- Help the user define metrics for database performance (e.g., query execution time, connection pool usage).
- Guide the user in configuring the aggregation tool to collect these metrics from the database.
- Assist in setting up alerts in the aggregation tool to notify the user when query execution time exceeds a defined threshold.
Best Practices
- Naming Conventions: Use a consistent and well-defined naming convention for all metrics to ensure clarity and ease of analysis.
