mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
OSDOCS-17454 [NETOBSERV] Module short descriptions for network-observability-operator-monitoring.adoc
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
2ae8f03ee7
commit
eb136b3903
@@ -6,7 +6,10 @@
|
||||
[id="network-observability-disable-alerts_{context}"]
|
||||
= Disabling health alerts
|
||||
|
||||
You can opt out of health alerting by editing the `FlowCollector` resource:
|
||||
[role="_abstract"]
|
||||
Disable specific health alerts, such as `NetObservLokiError` or `NetObservNoFlows`, by editing the `FlowCollector` resource and using the `spec.processor.metrics.disableAlerts` specification.
|
||||
|
||||
.Procedure
|
||||
|
||||
. In the web console, navigate to *Ecosystem* -> *Installed Operators*.
|
||||
. Under the *Provided APIs* heading for the *NetObserv Operator*, select *Flow Collector*.
|
||||
|
||||
@@ -5,7 +5,10 @@
|
||||
[id="network-observability-netobserv-dashboard-ebpf-agent-alerts_{context}"]
|
||||
= Using the eBPF agent alert
|
||||
|
||||
An alert, `NetObservAgentFlowsDropped`, is triggered when the network observability eBPF agent hashmap table is full or when the capacity limiter is triggered. If you see this alert, consider increasing the `cacheMaxFlows` in the `FlowCollector`, as shown in the following example.
|
||||
[role="_abstract"]
|
||||
Resolve the `NetObservAgentFlowsDropped` alert, which occurs when the eBPF agent hashmap is full, by increasing the `spec.agent.ebpf.cacheMaxFlows` value in the `FlowCollector` custom resource.
|
||||
|
||||
An alert, `NetObservAgentFlowsDropped`, is also triggered when the capacity limiter is triggered. If you see this alert, consider increasing the `cacheMaxFlows` in the `FlowCollector`, as shown in the following example.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
|
||||
@@ -6,6 +6,9 @@
|
||||
[id="network-observability-health-alert-overview_{context}"]
|
||||
= Health alerts
|
||||
|
||||
[role="_abstract"]
|
||||
Understand the health alerts generated by the Network Observability Operator, which trigger banners when conditions like Loki ingestion errors, zero flow ingestion, or dropped eBPF flows occur.
|
||||
|
||||
A health alert banner that directs you to the dashboard can appear on the *Network Traffic* and *Home* pages if an alert is triggered. Alerts are generated in the following cases:
|
||||
|
||||
* The `NetObservLokiError` alert occurs if the `flowlogs-pipeline` workload is dropping flows because of Loki errors, such as if the Loki ingestion rate limit has been reached.
|
||||
|
||||
@@ -6,7 +6,10 @@
|
||||
[id="network-observability-health-dashboard-overview_{context}"]
|
||||
= Health dashboards
|
||||
|
||||
Metrics about health and resource usage of the Network Observability Operator are located in the *Observe* -> *Dashboards* page in the web console. You can view metrics about the health of the Operator in the following categories:
|
||||
[role="_abstract"]
|
||||
View the Network Observability Operator health dashboards in the {product-title} web console to monitor the health status, resource usage, and internal statistics of the operator and its components.
|
||||
|
||||
Metrics are located in the *Observe* -> *Dashboards* page in the {product-title} web console. You can view metrics about the health of the Network Observability Operator in the following categories:
|
||||
|
||||
* *Flows per second*
|
||||
* *Sampling*
|
||||
|
||||
@@ -5,6 +5,9 @@
|
||||
[id="network-observability-netobserv-dashboard-rate-limit-alerts_{context}"]
|
||||
= Creating Loki rate limit alerts for the NetObserv dashboard
|
||||
|
||||
[role="_abstract"]
|
||||
Create a custom `AlertingRule` resource based on Loki metrics to monitor for and trigger alerts when the Loki ingestion rate limits are reached, indicated by HTTP 429 errors.
|
||||
|
||||
You can create custom alerting rules for the *Netobserv* dashboard metrics to trigger alerts when Loki rate limits have been reached.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
@@ -6,7 +6,8 @@
|
||||
[id="network-observability-dashboard-view_{context}"]
|
||||
= Viewing health information
|
||||
|
||||
You can access metrics about health and resource usage of the Network Observability Operator from the *Dashboards* page in the web console.
|
||||
[role="_abstract"]
|
||||
View the *Netobserv/Health* dashboard within the {product-title} web console to monitor the health status and resource usage of the Network Observability Operator and its components.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
|
||||
Reference in New Issue
Block a user