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

Capability to change envoy histogram buckets #6700

Closed
themkarimi opened this issue Oct 12, 2024 · 3 comments
Closed

Capability to change envoy histogram buckets #6700

themkarimi opened this issue Oct 12, 2024 · 3 comments
Labels
kind/question Categorizes an issue as a user question. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@themkarimi
Copy link

Is it possible to change envoy histogram buckets in contour? we have done this before in envoy using this configuration:

      histogram_bucket_settings:
        - match:
            safe_regex:
              google_re2: {}
              regex: ".*" 
          buckets:
            - 1
            - 10
            - 50
            - 250
            - 500
            - 1000
            - 5000     
@themkarimi themkarimi added kind/question Categorizes an issue as a user question. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. labels Oct 12, 2024
@jeengbe
Copy link

jeengbe commented Nov 19, 2024

Hi! I would be interested in contributing this change.

I'm not fully familiar with Contour's configuration philosophy, so I would appreciate some help regarding where exactly to place these configuration values and what to name them. metrics.envoy sounds like the right place to put this, but the scope would need to be expanded from "configuration for metrics server endpoints" to metric configuration too

Copy link

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

This bot triages Issues according to the following rules:

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

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • 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 Jan 21, 2025
Copy link

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

This bot triages Issues according to the following rules:

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

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Categorizes an issue as a user question. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants