Optional postgres server/address tags #1026
Closed
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.
Hi,
This PR adds an address_tag (boolean) option to the postgresql input, to configure if the server tag is created or not.
Default is current behavior where server tag is created.
My main usecase is to get cleaner graphite metric namespace. for example:
current ns: {prefix}.{host}.postgresql.dbname}.host=10_25_238_72_user=db_39_telegraf_dbname=telegraf.blks_read
with address_tag=false: {prefix}.storage-db-0.postgresql.{dbname}.blks_read