Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Zachary Kent commented on PDB-4876 Re: Metrics endpoint broken great, thank you for testing that! Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.370980.1599053609000.35272.1600101540029%40Atlassian.JIRA.
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Elof Ofel commented on PDB-4876 Re: Metrics endpoint broken Confirmed in the open-source version (in this case, puppetdb 5.2.15-1stretch). #grep ^CONFIG /etc/default/puppetdb CONFIG="/etc/puppetlabs/puppetdb/conf.d" I created the metrics.conf file above in this dir and ran 'systemctl restart puppetdb'. Now the v1 endpoint respond to queries again. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Elof Ofel commented on PDB-4876 Re: Metrics endpoint broken Thanks for your excellent answers! For completeness, I plan to test the above metrics.conf file in an open source Puppet, tomorrow or next week. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.370980.1599053609000.33141.1599688440622%40Atlassian.JIRA.
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4876 Metrics endpoint broken Change By: Zachary Kent Epic Link: PDB-4759 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.370980.1599053609000.31962.1599598080283%40Atlassian.JIRA.
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4876 Metrics endpoint broken Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.370980.1599053609000.31956.1599597960100%40Atlassian.JIRA.
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4876 Metrics endpoint broken Change By: Zachary Kent Team: HA Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.370980.1599053609000.31924.1599596940279%40Atlassian.JIRA.
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4876 Metrics endpoint broken Change By: Zachary Kent Labels: docs metrics Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.370980.1599053609000.31923.1599596940235%40Atlassian.JIRA.
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title
Zachary Kent commented on PDB-4876
Re: Metrics endpoint broken
Hi Elof Ofel, I was able to turn the v1 endpoint back on by creating a metrics.conf file in the /etc/puppetlabs/puppetdb/conf.d/ directory with the following contents.
metrics: {
metrics-webservice: {
mbeans: {
enabled: true
}
}
}
I did this in a Puppet Enterprise install so the location of your conf.d directory for PuppetDB might be slightly different. After this file is in place restarting the PuppetDB service should enable the v1 metrics directory. I was able to check this by hitting the http://127.0.0.1:8080/metrics/v1/mbeans endpoint which lists all available metrics. Hope that helps! We will be updating our docs to reflect this, thanks for raising the ticket!
Add Comment
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Elof Ofel commented on PDB-4876 Re: Metrics endpoint broken Hi Zachary Kent ! Thanks for this response. That explains it all. A manual test confirms what you wrote: http://localhost:8080/metrics/v2/read/puppetlabs.puppetdb.population:name=pct-resource-dupesrequest mbean "puppetlabs.puppetdb.population:name=pct-resource-dupes" type "read" value Value "151107/183659" timestamp 1599214647 status 200 The v2 metrics endpoint is working fine. Yes, updating the docs would help others in the same situation like me. Nowhere did I see any mention of v1 being disabled. For completeness in this ticket (and possibly also in your updated documentation), can you please add instructions on how to force the v1 endpoint back on? Add Comment
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Zachary Kent commented on PDB-4876 Re: Metrics endpoint broken Hello Elof Ofel, There was a cve linked in the PuppetDB 5.2.13 release notes which caused PuppetDB to disable the metrics/v1 endpoint by default. PuppetDB 5.2.13 release notes All uses of metrics/v1 can be replaced by a call to metrics/v2/read over localhost. Here are some docs for how things work in the metrics/v2/read endpoint: jolokia docs . You'll need to replace GET /metrics/v1/mbeans/ with GET /metrics/v2/read/. The response you get back will have a slightly different structure but contain the same information. The data that used to be returned from the v1 endpoint is now nested under a value key in the v2 version of the response. Looking into this I also noticed the PuppetDB docs for the metrics endpoint haven't been updated properly. We'll work on updating the docs now, sorry for the confusion. Hope that helps Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.370980.1599053609000.30269.1599156240171%40Atlassian.JIRA.
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title
Elof Ofel updated an issue
PuppetDB / PDB-4876
Metrics endpoint broken
Change By:
Elof Ofel
Strange bug: After I upgraded puppetdb from 5.2.12-1stretch to 5.2.15-1stretch, I can no longer access the metrics endpoint.All requests to /metrics/v1/mbeans/* get at "404 not found" response while requests to e.g. /pdb/query/v4/ work just fine (200 OK). Prior to Jun 30, my system (Debian 9) was running puppetdb 5.2.12-1stretch and everything was working fine.On Jun 30, an 'apt-get upgrade' upgraded puppet-agent, puppet5-release, puppetdb, puppetserver and puppetdb-termini:{noformat} dpkg.log.3.gz:2020-06-30 08:34:48 upgrade puppet-agent:amd64 5.5.18-1stretch 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:48 status half-configured puppet-agent:amd64 5.5.18-1stretchdpkg.log.3.gz:2020-06-30 08:34:48 status unpacked puppet-agent:amd64 5.5.18-1stretchdpkg.log.3.gz:2020-06-30 08:34:48 status half-installed puppet-agent:amd64 5.5.18-1stretchdpkg.log.3.gz:2020-06-30 08:34:50 status half-installed puppet-agent:amd64 5.5.18-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 configure puppet-agent:amd64 5.5.20-1stretch dpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64 5.5.20-1stretchdpkg.log.3.gz:2020-06-30 08:34:51 status unpacked puppet-agent:amd64
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Elof Ofel created an issue PuppetDB / PDB-4876 Metrics endpoint broken Issue Type: Bug Affects Versions: PDB 5.2.15 Assignee: Unassigned Components: PuppetDB Created: 2020/09/02 6:33 AM Environment: Debian 9 puppet-agent 5.5.20-1stretch amd64 puppet5-release 5.0.0-11stretch all puppetdb 5.2.15-1stretch all puppetdb-termini 5.2.15-1stretch all puppetexplorer 2.0.0-62 all puppetserver 5.3.13-1stretch all ruby-puppet-forge 2.2.2-2 all ruby-semantic-puppet 0.1.4-2 all Labels: metrics Priority: Normal Reporter: Elof Ofel Strange bug: After I upgraded puppetdb from 5.2.12-1stretch to 5.2.15-1stretch, I can no longer access the metrics endpoint. All requests to /metrics/v1/mbeans/* get at "404 not found" response while requests to e.g. /pdb/query/v4/ work just fine (200 OK). Prior to Jun 30, my system (Debian 9) was running puppetdb 5.2.12-1stretch and everything was working fine. On Jun 30, an 'apt-get upgrade' upgraded puppet-agent, puppet5-release, puppetdb, puppetserver and puppetdb-termini:
