-
Notifications
You must be signed in to change notification settings - Fork 43
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
Population metric names changed in PuppetDB 4.x #49
Comments
I've been scratching my head since yesterday trying to fix this, works mint now, thanks heaps! |
"Perfect!" If it were a real solution instead of a (rather nicely executed, I must admit) work-around, it'd be Perfect! ;-) |
This is a fix to address dalen#49.
Any idea when this is going to be released? The RewriteRule workaround doesn't work for me. |
The rewrite rule works, but should be fixed in the application code to generate the proper http request in the first place. please fix it |
For anyone using the spotify-puppetexplorer module, @jasonhancock's temp fix can be added to the apache class pretty easily: Edit: Fixed based on @dhs-rec's comment! 😄 class {'::puppetexplorer':
vhost_options => {
rewrites => [ { rewrite_rule => ['^/api/metrics/v1/mbeans/puppetlabs.puppetdb.query.population:type=default,name=(.*)$ https://%{HTTP_HOST}/api/metrics/v1/mbeans/puppetlabs.puppetdb.population:name=$1 [R=301,L]'] } ] }
}
} |
Final closing However, still doesn't work for me. I still get messages like this one when reloading the dashboard page:
|
I can confirm that the workaround does work, even in hiera:
|
Any news on the issue? Puppetexplorer is still unusable for me. |
Too sad this thing doesn't get officially released. |
Giving up... |
Thanks for sharing this fix jasonhancock. Worked like a charm for me. |
Thanks for the fix - after an additional |
This had me puzzled for a while. The Rewrite rule was not working. NB: This is only if you are arent using SSL Change
To
Works now! |
@shaunrampersad changing the rewrite rule to the following would work in both scenarios:
|
Population metric names changed in PuppetDB 4.x
https://docs.puppetlabs.com/puppetdb/4.0/api/metrics/v1/changes-from-puppetdb-v3.html#population-metrics
For example, the following metrics:
are now, respectively:
As I'm proxying puppetexplorer with Apache, the addition of a rewrite rule works around this for now:
The text was updated successfully, but these errors were encountered: