feat: add app_name in active connections metric, streamline app_name#891
Open
feat: add app_name in active connections metric, streamline app_name#891
Conversation
Adds the application name provided in the connection startup to the ClientHandler metadata, and emit it in telemetry events. Ensures ClientHandler always have the user-provided application_name or "", in proxy and non-proxy scenarios. Previously, the ClientHandler would default to the "Supavisor" app name when one was not provided. Ensures that the postgres-side backend always has "Supavisor" app name, regardless of what's the app_name supavisor-side.
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
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.
Adds the application name provided in the connection startup to the ClientHandler metadata, and emit it in telemetry events.
Ensures ClientHandler always have the user-provided application_name or "", in proxy and non-proxy scenarios.
Previously, the ClientHandler would default to the "Supavisor" app name when one was not provided. Ensures that the postgres-side backend always has "Supavisor" app name, regardless of what's the app_name supavisor-side.