feat: add max connections metric for each lb real server - #434
Open
sboschman wants to merge 1 commit into
Open
Conversation
Signed-off-by: Sverre Boschman <1142569+sboschman@users.noreply.github.com>
sboschman
force-pushed
the
lb-max-connections-metric
branch
from
August 10, 2026 14:02
4c5c7f7 to
796a3ae
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pr introduces a
fortigate_lb_real_server_max_connectionsmetric to accompany the existingfortigate_lb_real_server_active_sessionsmetric. Together they can be used to alert on hitting the configured connections limit.E.g. (promql)
fixes #433