Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 1. Monitoring APIs


1.1. Alertmanager [monitoring.coreos.com/v1]

Description
Alertmanager describes an Alertmanager cluster.
Type
object

1.2. AlertmanagerConfig [monitoring.coreos.com/v1beta1]

Description
AlertmanagerConfig configures the Prometheus Alertmanager, specifying how alerts should be grouped, inhibited and notified to external systems.
Type
object

1.3. AlertRelabelConfig [monitoring.openshift.io/v1]

Description
AlertRelabelConfig defines a set of relabel configs for alerts. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).
Type
object

1.4. AlertingRule [monitoring.openshift.io/v1]

Description
AlertingRule represents a set of user-defined Prometheus rule groups containing alerting rules. This resource is the supported method for cluster admins to create alerts based on metrics recorded by the platform monitoring stack in OpenShift, i.e. the Prometheus instance deployed to the openshift-monitoring namespace. You might use this to create custom alerting rules not shipped with OpenShift based on metrics from components such as the node_exporter, which provides machine-level metrics such as CPU usage, or kube-state-metrics, which provides metrics on Kubernetes usage. The API is mostly compatible with the upstream PrometheusRule type from the prometheus-operator. The primary difference being that recording rules are not allowed here — only alerting rules. For each AlertingRule resource created, a corresponding PrometheusRule will be created in the openshift-monitoring namespace. OpenShift requires admins to use the AlertingRule resource rather than the upstream type in order to allow better OpenShift specific defaulting and validation, while not modifying the upstream APIs directly. You can find upstream API documentation for PrometheusRule resources here: https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).
Type
object

1.5. PodMonitor [monitoring.coreos.com/v1]

Description
PodMonitor defines monitoring for a set of pods.
Type
object

1.6. Probe [monitoring.coreos.com/v1]

Description
Probe defines monitoring for a set of static targets or ingresses.
Type
object

1.7. Prometheus [monitoring.coreos.com/v1]

Description
Prometheus defines a Prometheus deployment.
Type
object

1.8. PrometheusRule [monitoring.coreos.com/v1]

Description
PrometheusRule defines recording and alerting rules for a Prometheus instance
Type
object

1.9. ServiceMonitor [monitoring.coreos.com/v1]

Description
ServiceMonitor defines monitoring for a set of services.
Type
object

1.10. ThanosRuler [monitoring.coreos.com/v1]

Description
ThanosRuler defines a ThanosRuler deployment.
Type
object

1.11. NodeMetrics [metrics.k8s.io/v1beta1]

Description
NodeMetrics sets resource usage metrics of a node.
Type
object

1.12. PodMetrics [metrics.k8s.io/v1beta1]

Description
PodMetrics sets resource usage metrics of a pod.
Type
object
Red Hat logoGithubRedditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

© 2024 Red Hat, Inc.