envoyproxy/envoy

Overload manager: per-timer triggers

Open

#40 589 ouverte le 5 août 2025

Voir sur GitHub
 (6 commentaires) (0 réactions) (0 assignés)C++ (5 373 forks)batch import
area/overload_managerenhancementhelp wantedno stalebot

Métriques du dépôt

Stars
 (27 997 stars)
Métriques de merge PR
 (Merge moyen 8j) (378 PRs mergées en 30 j)

Description

Title: * Overload manager: per-timer triggers*

Description:

It would be really useful if in the reduce_timeouts action, you could configure different triggers for each timer.

Currently, it's only possible configure a set of triggers for the whole reduce_timeouts action which then uses the max pressure across all the triggers.

Imagine if you could configure something like this:

actions {
  name: "envoy.overload_actions.reduce_timeouts"
  timer_scale_factors {
    timer: HTTP_DOWNSTREAM_CONNECTION_IDLE
    min_timeout {
      seconds: 1
    }
    triggers {
      name: "my.custom.resource1"
      ...
    }
  }
  timer_scale_factors {
    timer: HTTP_DOWNSTREAM_CONNECTION_MAX
    min_timeout {
      seconds: 1
    }
    triggers {
      name: "my.custom.resource2"
      ...
    }
  }
}

This would give you more granular control of each timer.

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Guide contributeur