Skip to content

overload_manager: make proactive resource monitors trigger actions#42018

Merged
ggreenway merged 3 commits intoenvoyproxy:mainfrom
ggreenway:proactive-trigger
Nov 22, 2025
Merged

overload_manager: make proactive resource monitors trigger actions#42018
ggreenway merged 3 commits intoenvoyproxy:mainfrom
ggreenway:proactive-trigger

Conversation

@ggreenway
Copy link
Copy Markdown
Member

Also, publish a resource pressure gauge like normal resource monitors.

Risk Level: Low
Testing: Added tests
Docs Changes: Docs never indicated that this shouldn't be the behavior, so no doc changes
Release Notes: Added
Platform Specific Features: None

Also, publish a resource pressure gauge like normal resource monitors.

Signed-off-by: Greg Greenway <ggreenway@apple.com>
@ggreenway
Copy link
Copy Markdown
Member Author

/retest

Signed-off-by: Greg Greenway <ggreenway@apple.com>
Signed-off-by: Greg Greenway <ggreenway@apple.com>
@ggreenway
Copy link
Copy Markdown
Member Author

/retest

Copy link
Copy Markdown
Contributor

@KBaichoo KBaichoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable to me -- IIRC these were originally designed from managing the allocation of as particular resource e.g. from the tryAllocateResource and deAllocResource e.g. to fail allocing a resource if we hit a limit.

I don't see a reason why we wouldn't want to extend it to also trigger actions based on pressure.

@ggreenway ggreenway merged commit b18b993 into envoyproxy:main Nov 22, 2025
24 checks passed
grnmeira pushed a commit to grnmeira/envoy that referenced this pull request Mar 20, 2026
…nvoyproxy#42018)

Also, publish a resource pressure gauge like normal resource monitors.

Signed-off-by: Greg Greenway <ggreenway@apple.com>
Signed-off-by: Gustavo <grnmeira@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants