Fix dotnet-counters command to explicitly specify Npgsql provider via --counters#467
Merged
Conversation
Updated command for monitoring Npgsql metrics with dotnet-counters.
roji
enabled auto-merge (squash)
July 21, 2026 00:04
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
2 participants
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.
The documentation currently shows a generic
dotnet counters monitorcommand. However, by default, this tool only displaysSystem.Runtimemetrics and does not automatically discover Npgsql counters.To successfully monitor Npgsql connection pool metrics, the provider name must be explicitly passed using the
--countersparameter. Without this flag, the Npgsql metrics are not displayed even if the application is actively using the database.This PR updates the command example to include
--counters Npgsql, ensuring users can view the metrics correctly.Before:
After: