Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[postgres] add support for relation schemas #1771

Merged
merged 8 commits into from
Jul 23, 2015
Merged

[postgres] add support for relation schemas #1771

merged 8 commits into from
Jul 23, 2015

Conversation

kostas0
Copy link
Contributor

@kostas0 kostas0 commented Jul 15, 2015

This change populates an additional tag for postgres relations containing the schema name. With this separate tag we can disambiguate metrics coming from same name tables but in separate schemas (e.g. staging vs production).

In addition we can now limit publishing to specific relation schemas via configuration.

Original issue #1496.

@remh
Copy link

remh commented Jul 15, 2015

Thanks Kostas !
Can you also update the postgres.yaml.example to explain how to use this feature and what parameters to use ?

@kostas0
Copy link
Contributor Author

kostas0 commented Jul 16, 2015

Added config syntax example.

#
# relations:
# - relation_name: another_table
# schemas: public prod
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

schemas should be a yaml list, instead of a space separated list

@kostas0
Copy link
Contributor Author

kostas0 commented Jul 17, 2015

Thanks for the suggestions, now updated, please take a look.

@remh
Copy link

remh commented Jul 23, 2015

Looks good to me!
Thanks!

remh pushed a commit that referenced this pull request Jul 23, 2015
[postgres] add support for relation schemas
@remh remh merged commit 17a56fa into DataDog:master Jul 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants