Esta página se tradujo automáticamente. Leer el original en inglés.

Recipe

prometheus-chart

Prometheus metrics server on Kubernetes via the prometheus-community Helm chart, configured as one server: the chart's alerting, exporter and push-gateway subcharts are switched off. It renders a Deployment, a ConfigMap carrying the scrape configuration, a PersistentVolumeClaim for the time-series database, a ClusterIP Service, and the ServiceAccount, ClusterRole and ClusterRoleBinding the server reads the cluster's own endpoints under. The server image and the chart version are pinned. That cluster-scoped read grant also serves the chart's own jobs, which scrape whatever the cluster advertises through scrape annotations. Each connection on the `scrape_target` uses-socket becomes one scrape job, as on the workload-synthesis realization: a target publishing `metrics_endpoint` is scraped at that address; one publishing `metrics_service` or `metrics_pod_selector` is discovered in the namespace its connection's `aggrega.ai/namespace` annotation names, in every namespace for KEDA and Knative Serving, or in the server's own where neither declares one; a target publishing none halts the build. A connection's `credential` is mounted as a file through `server.extraSecretMounts`, and its job presents it as a bearer token. Reach for it where a chart repository is reachable and the server should discover targets beyond those wired, and for `prometheus` where the build must fetch nothing. With `infra.external_base_url` set, the server takes it as its external URL through the chart's `server.baseURL` and is kept serving at its root. With `values.otlp_receiver` true, `server.extraArgs` also turns on the OTLP receiver, whose address it publishes as provides.otlp_http_endpoint.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:64fdfa6f4b01166fe10b30871536485d8a880fb0e5d9a2a4e6f7fbdd02de2268
Publicado
2026-11-10T10:26:36Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:1582d481ed342cf1513e9bd39ca039f760a94b1d2f70f4522250c043c1b1a636

Referencia en esta versión

oci://hub.aggrega.ai/recipe/helm/prometheus-chart:1.0.0
Destino
—
Implementa
core/observability/prometheus:1.0.0

Proporciona

Plantillas de punteros deterministas que esta receta cablea para los consumidores.

NombrePlantilla
host{{ .context.rendered_name }}
port{{ .infra.port }}
protocolhttp
otlp_http_endpoint{{ if .values.otlp_receiver }}http://{{ .context.rendered_name }}:{{ .infra.port }}/api/v1/otlp{{ end }}
metrics_endpointhttp://{{ .context.rendered_name }}:{{ .infra.port }}/metrics

Workload

No se declaró ninguna plantilla de carga de trabajo.

Variables locales

No se declararon variables locales.

Mapeo de valores

No se declaró ningún mapeo de valores.

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

  • implementaimplementacontrato compatible

    core/observability/prometheus:1.0.0

    Todas las salidas obligatorias se satisfacen y cada salida proporcionada está nombrada en el contrato.

Usado por

Nada en el catálogo depende de esta entidad.

Referencia del concepto Recipe →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad