Skip to content

[release-1.11] Documentation update, health rules polishing#2400

Merged
jotak merged 4 commits intonetobserv:release-1.11from
openshift-cherrypick-robot:cherry-pick-2389-to-release-1.11
Feb 2, 2026
Merged

[release-1.11] Documentation update, health rules polishing#2400
jotak merged 4 commits intonetobserv:release-1.11from
openshift-cherrypick-robot:cherry-pick-2389-to-release-1.11

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #2389

/assign jotak

jotak added 4 commits February 2, 2026 11:56
- Rename IngressLatencyTrend => IngressHTTPLatencyTrend to distinguish
  with our other TCP latency
- Mark InstallDemoLoki as Unsupported
- Rename Alerts.md => HealthRules.md, and refresh its content; link to
  runbooks for details
@openshift-ci
Copy link

openshift-ci bot commented Feb 2, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mffiedler for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link

openshift-ci bot commented Feb 2, 2026

Hi @openshift-cherrypick-robot. Thanks for your PR.

I'm waiting for a netobserv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@codecov
Copy link

codecov bot commented Feb 2, 2026

Codecov Report

❌ Patch coverage is 62.50000% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 71.90%. Comparing base (bba6e99) to head (3fb5e02).
⚠️ Report is 3 commits behind head on release-1.11.

Files with missing lines Patch % Lines
internal/pkg/metrics/alerts/alerts.go 33.33% 2 Missing ⚠️
...lector/v1beta2/flowcollector_validation_webhook.go 50.00% 1 Missing ⚠️
Additional details and impacted files
@@              Coverage Diff              @@
##           release-1.11    #2400   +/-   ##
=============================================
  Coverage         71.89%   71.90%           
=============================================
  Files                93       93           
  Lines             10501    10501           
=============================================
+ Hits               7550     7551    +1     
+ Misses             2471     2470    -1     
  Partials            480      480           
Flag Coverage Δ
unittests 71.90% <62.50%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...flowcollector/v1beta2/flowcollector_alert_types.go 97.59% <100.00%> (ø)
api/flowcollector/v1beta2/flowcollector_types.go 100.00% <ø> (ø)
internal/pkg/metrics/alerts/builder.go 78.40% <100.00%> (ø)
...lector/v1beta2/flowcollector_validation_webhook.go 72.29% <50.00%> (ø)
internal/pkg/metrics/alerts/alerts.go 87.05% <33.33%> (ø)

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jotak jotak merged commit 8801688 into netobserv:release-1.11 Feb 2, 2026
7 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants