automotive-monitoring

Configures Prometheus scrape jobs for automotive Kubernetes services and fleet edge gateways.

7|2|Updated May 19, 2026
One-click install
npx skills add https://github.com/pangzhenying2025/hermes-automotive-skills --skill automotive-monitoring-pangzhenying2025
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: automotive-monitoring
Source: https://github.com/pangzhenying2025/hermes-automotive-skills/tree/main/skills/automotive-monitoring
Command: npx skills add https://github.com/pangzhenying2025/hermes-automotive-skills --skill automotive-monitoring-pangzhenying2025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up metrics collection for automotive cloud backends requires writing complex Prometheus scrape configurations across Kubernetes clusters, namespaces, and edge gateways, which is error-prone when done by hand. ## Core Features & Use Cases - Kubernetes Service Discovery: Prebuilt scrape jobs for API servers, nodes, cAdvisor, service endpoints, and pods using kubernetes_sd_configs with relabeling rules. - Automotive Service Monitoring: Dedicated jobs for ADAS processing and battery analytics services across production and staging namespaces. - Fleet Edge Collection: Static scrape targets for edge gateways with labeled metrics for fleet-level observability. - Use Case: Deploy this configuration to a Prometheus server in your automotive platform cluster to immediately begin collecting metrics from ADAS and battery services without writing relabeling rules from scratch. ## Quick Start Apply the included prometheus.yml to your Prometheus deployment to start scraping metrics from the automotive Kubernetes services and edge gateways.

Frequently Asked Questions about automotive-monitoring

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

FAQPage Schema
How do I configure Prometheus to monitor Kubernetes pods?▼

Use kubernetes_sd_configs with the pod role and relabel_configs that keep pods annotated with prometheus.io/scrape. The configuration maps annotation-defined ports and paths into scrape targets automatically.

How to scrape metrics from specific Kubernetes namespaces with Prometheus?▼

Restrict discovery by listing namespace names under the kubernetes_sd_configs namespaces field. This configuration targets automotive-production and automotive-staging namespaces for ADAS and battery services.

What relabeling rules are needed for Prometheus Kubernetes service discovery?▼

Typical rules keep targets matching annotation or label regexes, rewrite __address__ with the metrics port, and map Kubernetes labels to metric labels via labelmap actions. The provided jobs demonstrate each pattern.

Does this Prometheus configuration work with the Prometheus Operator?▼

Yes, it includes a ServiceMonitor-style job for the ADAS processing service that honors labels and filters endpoints by the metrics port name, matching Prometheus Operator conventions.

How do I monitor edge gateways with Prometheus?▼

Define a static_configs job listing each gateway host and port, then use relabeling to attach an identifying label such as edge_gateway. This configuration scrapes two edge gateways on port 9090.