Initial commit

This commit is contained in:
Zhongwei Li
2025-11-30 08:21:10 +08:00
commit 5641014dde
8 changed files with 199 additions and 0 deletions

View File

@@ -0,0 +1,15 @@
{
"name": "metrics-aggregator",
"description": "Aggregate and centralize performance metrics",
"version": "1.0.0",
"author": {
"name": "Claude Code Plugins",
"email": "[email protected]"
},
"skills": [
"./skills"
],
"commands": [
"./commands"
]
}

3
README.md Normal file
View File

@@ -0,0 +1,3 @@
# metrics-aggregator
Aggregate and centralize performance metrics

View File

@@ -0,0 +1,35 @@
---
description: Aggregate performance metrics centrally
---
# Metrics Aggregator
Implement centralized metrics aggregation for comprehensive performance visibility.
## Metric Categories
1. **Application Metrics**: Custom business and performance metrics
2. **System Metrics**: CPU, memory, disk, network
3. **Database Metrics**: Query performance, connections
4. **Cache Metrics**: Hit rates, memory usage
5. **Queue Metrics**: Message rates, processing times
6. **External Service Metrics**: Third-party API performance
## Process
1. Design metrics taxonomy and naming convention
2. Choose metrics platform (Prometheus, StatsD, CloudWatch, etc.)
3. Implement metric instrumentation
4. Configure aggregation and retention
5. Create visualization dashboards
6. Set up alerting on key metrics
## Output
Provide:
- Metrics instrumentation code
- Metric naming and tagging standards
- Collection configuration (Prometheus, etc.)
- Aggregation rules and retention policies
- Dashboard configurations (Grafana, etc.)
- Alert definitions for critical metrics

61
plugin.lock.json Normal file
View File

@@ -0,0 +1,61 @@
{
"$schema": "internal://schemas/plugin.lock.v1.json",
"pluginId": "gh:jeremylongshore/claude-code-plugins-plus:plugins/performance/metrics-aggregator",
"normalized": {
"repo": null,
"ref": "refs/tags/v20251128.0",
"commit": "96ae727be15bd0d921b8f8bb4d4cf67554fbcc35",
"treeHash": "8f939abc8d648410a1dfb071f340714e5754d4c6eeb18b46f953089324ffd195",
"generatedAt": "2025-11-28T10:18:34.303483Z",
"toolVersion": "publish_plugins.py@0.2.0"
},
"origin": {
"remote": "git@github.com:zhongweili/42plugin-data.git",
"branch": "master",
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
},
"manifest": {
"name": "metrics-aggregator",
"description": "Aggregate and centralize performance metrics",
"version": "1.0.0"
},
"content": {
"files": [
{
"path": "README.md",
"sha256": "9ff2b6089ab0477daa2937776850742f0f6a76a50eeca80065a03c2b376355be"
},
{
"path": ".claude-plugin/plugin.json",
"sha256": "155bb5fcd08e3c5c667f2f279d76bb857b48098dc3855f0da45f950aa05f87f9"
},
{
"path": "commands/aggregate-metrics.md",
"sha256": "b37c36561d9d0ebfd026c782454abed246f2d3972a5fa8bd8d0c3472f641249d"
},
{
"path": "skills/metrics-aggregator/SKILL.md",
"sha256": "26121ded1be7007d0d74853256ea58d53c6445db358cb6f66ed4e5e269cc5b96"
},
{
"path": "skills/metrics-aggregator/references/README.md",
"sha256": "3feda01d6f963c356d7ef5c8eebd6113f7a1c111f3ae1b113b00fd96d5353486"
},
{
"path": "skills/metrics-aggregator/scripts/README.md",
"sha256": "c84ba6d01d16c3d461de18901fc52df60e7de88a8aeb8bf1786eb5cf681992e0"
},
{
"path": "skills/metrics-aggregator/assets/README.md",
"sha256": "58085a17e1def31eead80d46b63f26f439599c116bb0800d6c9481bf0f6a8794"
}
],
"dirSha256": "8f939abc8d648410a1dfb071f340714e5754d4c6eeb18b46f953089324ffd195"
},
"security": {
"scannedAt": null,
"scannerVersion": null,
"flags": []
}
}

View File

@@ -0,0 +1,55 @@
---
name: aggregating-performance-metrics
description: |
This skill enables Claude to aggregate and centralize performance metrics from various sources. It is used when the user needs to consolidate metrics from applications, systems, databases, caches, queues, and external services into a central location for monitoring and analysis. The skill is triggered by requests to "aggregate metrics", "centralize performance metrics", or similar phrases related to metrics aggregation and monitoring. It facilitates designing a metrics taxonomy, choosing appropriate aggregation tools, and setting up dashboards and alerts.
allowed-tools: Read, Write, Bash, Grep
version: 1.0.0
---
## 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
1. **Metrics Taxonomy Design**: Claude assists in defining a clear and consistent naming convention for metrics across all systems.
2. **Aggregation Tool Selection**: Claude helps select the appropriate metrics aggregation tool (e.g., Prometheus, StatsD, CloudWatch) based on the user's environment and requirements.
3. **Configuration and Integration**: Claude guides the configuration of the chosen aggregation tool and its integration with various data sources.
4. **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:
1. Guide the user in defining metrics for applications (e.g., request latency, error rates) and systems (e.g., CPU usage, memory utilization).
2. 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:
1. Help the user define metrics for database performance (e.g., query execution time, connection pool usage).
2. Guide the user in configuring the aggregation tool to collect these metrics from the database.
3. 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.
- **Granularity**: Choose an appropriate level of granularity for metrics to balance detail and storage requirements.
- **Retention Policies**: Define retention policies for metrics to manage storage space and ensure data is available for historical analysis.
## Integration
This skill integrates with other Claude Code plugins that manage infrastructure, deploy applications, and monitor system health. For example, it can be used in conjunction with a deployment plugin to automatically configure metrics collection after a new application deployment.

View File

@@ -0,0 +1,9 @@
# Assets
Bundled resources for metrics-aggregator skill
- [ ] grafana_dashboard_template.json: A template for creating Grafana dashboards with pre-configured panels and visualizations for common metrics.
- [ ] datadog_dashboard_template.json: A template for creating Datadog dashboards with pre-configured panels and visualizations for common metrics.
- [ ] splunk_dashboard_template.xml: A template for creating Splunk dashboards with pre-configured panels and visualizations for common metrics.
- [ ] example_metrics_data.json: Example JSON data representing collected metrics from various sources.
- [ ] metrics_schema.json: A JSON schema defining the structure and data types of collected metrics.

View File

@@ -0,0 +1,13 @@
# References
Bundled resources for metrics-aggregator skill
- [ ] metrics_naming_standards.md: Defines the naming conventions for metrics to ensure consistency and clarity across different systems and applications.
- [ ] metrics_aggregation_configuration.md: Provides detailed configuration options for metrics aggregation, including time intervals, dimensions, and aggregation functions.
- [ ] prometheus_integration.md: Documents the steps to integrate with Prometheus, including configuring exporters and setting up data sources.
- [ ] statsd_integration.md: Documents the steps to integrate with StatsD, including configuring clients and setting up data sources.
- [ ] cloudwatch_integration.md: Documents the steps to integrate with CloudWatch, including configuring agents and setting up data sources.
- [ ] grafana_dashboard_setup.md: Provides instructions on setting up Grafana dashboards to visualize aggregated metrics.
- [ ] datadog_dashboard_setup.md: Provides instructions on setting up Datadog dashboards to visualize aggregated metrics.
- [ ] splunk_dashboard_setup.md: Provides instructions on setting up Splunk dashboards to visualize aggregated metrics.
- [ ] alert_definitions.md: Defines the process for creating and managing alerts based on aggregated metrics, including thresholds, notification channels, and escalation policies.

View File

@@ -0,0 +1,8 @@
# Scripts
Bundled resources for metrics-aggregator skill
- [ ] metrics_collection.py: Automates the collection of metrics from various sources (Prometheus, StatsD, CloudWatch) using their respective APIs or SDKs.
- [ ] metrics_validation.py: Validates collected metrics against predefined schemas or thresholds to ensure data quality and consistency.
- [ ] metrics_aggregation.py: Aggregates metrics based on specified time intervals (e.g., hourly, daily, weekly) and dimensions (e.g., application, system, region).
- [ ] metrics_export.py: Exports aggregated metrics to various monitoring and analysis platforms (e.g., Grafana, Datadog, Splunk) using their respective APIs or SDKs.