Chapter 11. Monitoring the Network Observability Operator

Procedure

1. From the Administrator perspective in the web console, navigate to Observe Dashboards.
2. From the Dashboards dropdown, select Netobserv/Health.
3. View the metrics about the health of the Operator that are displayed on the page.

Procedure

1. Create a YAML file by clicking the import icon, +.

2. Add an alerting rule configuration to the YAML file. In the YAML sample that follows, an alert is created for when Loki rate limits have been reached:

   apiVersion: monitoring.openshift.io/v1
   kind: AlertingRule
   metadata:
     name: loki-alerts
     namespace: openshift-monitoring
   spec:
     groups:
     - name: LokiRateLimitAlerts
       rules:
       - alert: LokiTenantRateLimit
         annotations:
           message: |-
             {{ $labels.job }} {{ $labels.route }} is experiencing 429 errors.
           summary: "At any number of requests are responded with the rate limit error code."
         expr: sum(irate(loki_request_duration_seconds_count{status_code="429"}[1m])) by (job, namespace, route) / sum(irate(loki_request_duration_seconds_count[1m])) by (job, namespace, route) * 100 > 0
         for: 10s
         labels:
           severity: warning

   Copy to Clipboard Toggle word wrap
3. Click Create to apply the configuration file to the cluster.

Procedure

1. In the web console, navigate to Operators Installed Operators.
2. Under the Provided APIs heading for the Network Observability Operator, select Flow Collector.
3. Select cluster, and then select the YAML tab.
4. Increase the spec.agent.ebpf.cacheMaxFlows value, as shown in the following YAML sample: