cobalt-core

A KVM exporter collects libvirt and cgroups data by interfacing with the hypervisor to extract resource metrics, which are then exposed for Prometheus scraping. The cobaltcore reference materials detail specific data flow, collection mechanisms, and metric labeling semantics.

Troubleshooting KVM hypervisor metrics exporter behavior involves checking configuration variables, deployment models, and concurrency constraints detailed in the cobaltcore references. The Skill loads repo-specific architecture data to diagnose operational issues rather than providing generic Kubernetes guidance.

The cobaltcore kvm-exporter exposes specific hypervisor metrics and labels defined in its curated metric catalog. The Skill loads reference materials to provide exact metric naming semantics, label structures, and configuration variables for interpreting the exported data accurately.

Yes, cobaltcore infrastructure references support planning KVM exporter configuration and deployment approaches by providing repo-specific architecture details, deployment models, and concurrency constraints. The Skill identifies target components and loads matching references to deliver specific configuration guidance.

Generic answers occur when target cobaltcore components are not properly identified by signal keywords. The Skill prevents this by greedily loading matching reference materials based on detected keywords, ensuring responses are grounded in repo-specific architecture instead of guess-based guidance.