project-prometheus-profiles

Create, validate, and install Netdata Prometheus collector chart profiles for infrastructure monitoring.

80.4k|6.6k|Updated Jun 17, 2013
One-click install
npx skills add https://github.com/netdata/netdata --skill project-prometheus-profiles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-prometheus-profiles
Source: https://github.com/netdata/netdata/tree/main/.agents/skills/project-prometheus-profiles
Command: npx skills add https://github.com/netdata/netdata --skill project-prometheus-profiles

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complexity of mapping raw Prometheus metrics to meaningful operator dashboards, ensuring that infrastructure monitoring is both accurate and actionable without manual, error-prone configuration.

Core Features & Use Cases

  • Profile Authoring: Design Prometheus collector chart profiles with clear entity grains, hierarchy, and aggregation logic.
  • Objective Validation: Use built-in scripts to prove schema compatibility, cardinality boundaries, and production collector path integrity.
  • Use Case: When onboarding a new Prometheus-based exporter, use this Skill to define how metrics like latency, error rates, and saturation are visualized, ensuring consistent operator experience across your infrastructure.

Quick Start

Use the project-prometheus-profiles skill to validate the new prometheus profile located at path/to/profile.yaml using the metrics dump at path/to/metrics.prom.

Frequently Asked Questions about project-prometheus-profiles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Prometheus profile for Netdata?

Define your profile in a YAML file following the Prometheus profile schema, then use the provided validate-profile.py script to ensure your configuration meets schema and runtime requirements.

What is the purpose of the objective validator?

The objective validator proves that your profile schema is compatible with the production collector, planner, and emitter path, ensuring that your metrics are correctly ingested and rendered.

How should I handle high-cardinality labels in my profile?

Assign labels explicit roles such as identity, dimension, or promoted metadata. Avoid using high-cardinality labels like request IDs or IP addresses for chart identity to maintain dashboard performance.

Can I use this skill to test profiles against live data?

Yes, you can install a user profile under the configured directory and verify collector selection, chart values, and hierarchy against a live target, provided you follow the delivery guidelines.

Why does my profile validation report a warning?

Warnings often indicate potential UX issues like deep hierarchies or ambiguous family structures. Investigate these warnings to ensure your dashboard remains intuitive for operators.