Support multiple Postgres instances #110
Conversation
puppet_metrics_dashboard::profile::master::postgres is a typethat may have no external impact to Forge modules. This module is declared in 0 of 575 indexed public
|
|
@seanmil Thank you for submitting these PRs! It looks like the spec tests are broken. We will fix those and ask you to rebase these once fixed. |
Thanks. I saw the failures and took a very quick look at what was causing them, but we are nearly all EL and so I don't have much familiarity with the |
|
The issue is in being tracked in #115. I should have a PR up in the morning to fix it. |
Tag the data with the name of the Postgres server instead of the server performing the data collection.
Include the server name in all aliases so the data points can be identified back to their server. Add a '$server' variable allowing selection of the systems to show based on the tag values.
seanmil
force-pushed
the
multiple_postgres
branch
from
7972025
to
dba6fc7
Compare
@jarretlavallee done! thanks! |
In a PE DR setup there are two active Postgres instances. Currently multiple Postgres instances are not handled well in terms of data collection nor graphing. This change ensures that the data is properly tagged with the Postgres server name as well as updating the graphs for multi-server support based on the server tag.