Skip to content

Netobserv: rename IngressLatencyTrend => IngressHTTPLatencyTrend #387

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jotak wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Netobserv: rename IngressLatencyTrend => IngressHTTPLatencyTrend #387

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions ...rvability-operator/IngressLatencyTrend.md → ...ility-operator/IngressHTTPLatencyTrend.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# IngressLatencyTrend
# IngressHTTPLatencyTrend

## Meaning

The `IngressLatencyTrend` alert template is triggered when Network
The `IngressHTTPLatencyTrend` alert template is triggered when Network
Observability detects a significant increase in HAProxy ingress response
latency compared to a baseline from the past. This is a trend-based alert that
compares current latency against historical values. This template can generate
Expand All @@ -11,13 +11,13 @@ custom resource.

**Possible alert variants:**

- `IngressLatencyTrend_Critical` - Global cluster-wide ingress latency
- `IngressHTTPLatencyTrend_Critical` - Global cluster-wide ingress latency
increase exceeds critical threshold compared to baseline
- `IngressLatencyTrend_Warning` - Global cluster-wide ingress latency increase
- `IngressHTTPLatencyTrend_Warning` - Global cluster-wide ingress latency increase
exceeds warning threshold compared to baseline
- `IngressLatencyTrend_Info` - Global cluster-wide ingress latency increase
- `IngressHTTPLatencyTrend_Info` - Global cluster-wide ingress latency increase
exceeds info threshold compared to baseline
- `IngressLatencyTrend_PerDstNamespace{Critical,Warning,Info}` - Ingress
- `IngressHTTPLatencyTrend_PerDstNamespace{Critical,Warning,Info}` - Ingress
latency increase for traffic destined to a specific namespace exceeds
threshold

Expand Down Expand Up @@ -48,7 +48,7 @@ spec:
processor:
metrics:
healthRules:
- template: IngressLatencyTrend
- template: IngressHTTPLatencyTrend
mode: Recording
variants:
- groupBy: Namespace
Expand Down Expand Up @@ -87,7 +87,7 @@ spec:
processor:
metrics:
healthRules:
- template: IngressLatencyTrend
- template: IngressHTTPLatencyTrend
mode: Alert
variants:
- groupBy: Namespace
Expand All @@ -109,7 +109,7 @@ spec:
processor:
metrics:
healthRules:
- template: IngressLatencyTrend
- template: IngressHTTPLatencyTrend
mode: Alert
variants:
- groupBy: Namespace
Expand All @@ -122,20 +122,20 @@ spec:

### Disable this alert entirely

To completely disable IngressLatencyTrend alerts:
To completely disable IngressHTTPLatencyTrend alerts:

```bash
oc edit flowcollector cluster
```

Add IngressLatencyTrend to the disableAlerts list:
Add IngressHTTPLatencyTrend to the disableAlerts list:

```yaml
spec:
processor:
metrics:
disableAlerts:
- IngressLatencyTrend
- IngressHTTPLatencyTrend
```

For more information on configuring Network Observability alerts and
Expand Down