Skip to content
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.

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

Add per route metrics option #6531

Conversation

rtreffer-rddt
Copy link

This is a continuation of #5535

I made sure I keep all signed-off and author attributions intact, I added a signed-off when I changed things. The rebase required mostly a change from ref.To to ptr.To.

There is one significant addition. HTTPProxy objects can define multiple routes, so we would need a way to distinguish routes. For that I'll per default generate a router+index suffix (route0, route1, ...). There is optionally also support for a RouteTag that can be used for semantic names.

Fixes #4637

@rtreffer-rddt rtreffer-rddt requested a review from a team as a code owner June 28, 2024 11:34
@rtreffer-rddt rtreffer-rddt requested review from tsaarni and skriss and removed request for a team June 28, 2024 11:34
@sunjayBhatia sunjayBhatia requested review from a team, davinci26 and clayton-gonsalves and removed request for a team June 28, 2024 11:34
Copy link

Hi @rtreffer-rddt! Welcome to our community and thank you for opening your first Pull Request. Someone will review it soon. Thank you for committing to making Contour better. You can also join us on our mailing list and in our channel in the Kubernetes Slack Workspace

Copy link

codecov bot commented Jun 28, 2024

Codecov Report

Attention: Patch coverage is 52.17391% with 11 lines in your changes missing coverage. Please review.

Project coverage is 81.72%. Comparing base (f9b6f6f) to head (7ffaa29).
Report is 31 commits behind head on main.

Files with missing lines Patch % Lines
internal/dag/gatewayapi_processor.go 0.00% 2 Missing and 2 partials ⚠️
internal/dag/httpproxy_processor.go 75.00% 1 Missing and 1 partial ⚠️
internal/dag/ingress_processor.go 0.00% 1 Missing and 1 partial ⚠️
internal/envoy/v3/route.go 0.00% 1 Missing and 1 partial ⚠️
cmd/contour/serve.go 75.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #6531      +/-   ##
==========================================
- Coverage   81.76%   81.72%   -0.05%     
==========================================
  Files         133      133              
  Lines       15942    15964      +22     
==========================================
+ Hits        13035    13046      +11     
- Misses       2614     2620       +6     
- Partials      293      298       +5     
Files with missing lines Coverage Δ
cmd/contour/servecontext.go 85.98% <100.00%> (+0.03%) ⬆️
internal/contourconfig/contourconfiguration.go 98.70% <100.00%> (+<0.01%) ⬆️
internal/dag/dag.go 98.44% <ø> (ø)
pkg/config/parameters.go 88.07% <100.00%> (+0.04%) ⬆️
cmd/contour/serve.go 22.97% <75.00%> (+0.30%) ⬆️
internal/dag/httpproxy_processor.go 91.28% <75.00%> (-0.12%) ⬇️
internal/dag/ingress_processor.go 97.10% <0.00%> (-0.95%) ⬇️
internal/envoy/v3/route.go 79.78% <0.00%> (-0.26%) ⬇️
internal/dag/gatewayapi_processor.go 93.60% <0.00%> (-0.27%) ⬇️

@clayton-gonsalves clayton-gonsalves added the release-note/minor A minor change that needs about a paragraph of explanation in the release notes. label Jul 2, 2024
Copy link

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 14d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

  • Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
  • Mark this PR as fresh by commenting or pushing a commit
  • Close this PR
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 17, 2024
therealak12 and others added 6 commits August 15, 2024 14:36
Signed-off-by: Ahmad Karimi <ak12hastam@gmail.com>
Signed-off-by: René Treffer <rene.treffer@reddit.com>
Signed-off-by: Ahmad Karimi <ak12hastam@gmail.com>
Signed-off-by: René Treffer <rene.treffer@reddit.com>
Signed-off-by: Ahmad Karimi <ak12hastam@gmail.com>
Routes in an HTTPProxy object are a list. For metrics purposes
these should be distinguishable.

We can number them by route index (route0, route1, route2....) and
optionally allow a RouteTag override (e.g. login).

Signed-off-by: René Treffer <rene.treffer@reddit.com>
Signed-off-by: René Treffer <rene.treffer@reddit.com>
Signed-off-by: René Treffer <rene.treffer@reddit.com>
@rtreffer-rddt
Copy link
Author

Rebased on latest main branch

@tsaarni tsaarni removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 15, 2024
Signed-off-by: René Treffer <rene.treffer@reddit.com>
Copy link

github-actions bot commented Sep 2, 2024

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 14d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

  • Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
  • Mark this PR as fresh by commenting or pushing a commit
  • Close this PR
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 2, 2024
Copy link

github-actions bot commented Oct 3, 2024

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 14d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

  • Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
  • Mark this PR as fresh by commenting or pushing a commit
  • Close this PR
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot closed this Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. release-note/minor A minor change that needs about a paragraph of explanation in the release notes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Contour support for Envoy's stats per route
4 participants