Re: [Puppet Users] PuppetDB latest version has disabled APIv1 metrics

2020-03-15 Thread comport3
Actually attempting to add the mentioned config to file '/etc/puppetlabs/puppetserver/conf.d/metrics.conf' results in the puppetserver service being unable to start, and this is logged - clojure.lang.ExceptionInfo: Value does not match schema: {:metrics-webservice {:mbeans disallowed-key}} --

Re: [Puppet Users] PuppetDB latest version has disabled APIv1 metrics

2020-03-15 Thread comport3
Thanks for this info, I think it points in the right direction. Are you able to provide any example config or a link to how to action this? It's not immediately obvious. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this

Re: [Puppet Users] PuppetDB latest version has disabled APIv1 metrics

2020-03-13 Thread Justin Stoller
I believe a config value was added at: metrics.metrics-webservice.mbeans.enabled to match the jolokia one that controls v2. However the default for the mbeans / v1 endpoint is now `false`. Note that this is now the case for Puppet Server as well and can be re-enabled with the same config value in

[Puppet Users] PuppetDB latest version has disabled APIv1 metrics

2020-03-12 Thread comport3
The latest version of PuppetDB v6.9.1 has removed localhost access to the v1 API metrics. Ref https://puppet.com/security/cve/CVE-2020-7943/ https://puppet.com/docs/puppet/latest/release_notes_puppet.html#puppet-resolved-issues-x.12.0 Given it's only "disabled by default", this suggests there is