PuppetDB 2.3 shows ? for "Collection Queries"

84 views
Skip to first unread message

Lori Cho

unread,
Sep 30, 2015, 5:25:31 PM9/30/15
to Puppet Users
We are using puppetdb 2.3.4 with postgres.  

When looking at the dashboard, the following only shows '?', "Collection Queries", "Enqueuing", "DLO Compression", "DLO Size on Disk", "Discarded Messages".  

Can someone advise as to why this might be?  


Wyatt Alt

unread,
Sep 30, 2015, 6:32:30 PM9/30/15
to puppet...@googlegroups.com, Lori Cho
> --
> You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to puppet-users...@googlegroups.com
> <mailto:puppet-users...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/0bf238ac-7b43-4c40-b4b8-6b680feb9417%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/0bf238ac-7b43-4c40-b4b8-6b680feb9417%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

Hi Lori,
The issue with "Collection Queries" and "Enqueuing" is a known bug
that's described here:
https://tickets.puppetlabs.com/browse/PDB-1113

it's been fixed on PDB 3.x. Under working conditions those represent how
long it takes to query PDB's resources endpoint, and to post commands to
PDB.

The DLO-related metrics relate to failed commands, and they are
appearing as ? because none of your commands have failed, and thus the
dead letter office (DLO) does not yet exist. If you want to verify that
it works, you can cause a command failure by posting a report to the
commands endpoint twice (this will fail because of a constraint
violation, and cause some log noise as the command is retried).
https://gist.github.com/40b4acfb4ea4c6776478

Wyatt

Wyatt Alt

unread,
Sep 30, 2015, 6:35:14 PM9/30/15
to puppet...@googlegroups.com, Lori Cho
By the way, doing that would also put some useless data in your database
when it succeeds on the first submission, so I wouldn't actually try it
unless you're on a test system.

Wyatt

Lori Cho

unread,
Sep 30, 2015, 11:06:01 PM9/30/15
to Wyatt Alt, puppet...@googlegroups.com
How come the ticket is still open if fixed?? I came across that when googling earlier but with no responses to the ticket it was unclear what to make of it.

Wyatt Alt

unread,
Oct 1, 2015, 12:38:58 PM10/1/15
to Lori Cho, puppet...@googlegroups.com
On 9/30/15 8:05 PM, Lori Cho wrote:
> How come the ticket is still open if fixed?? I came across that when googling earlier but with no responses to the ticket it was unclear what to make of it.
It was fixed incidentally in unrelated work. I've closed the ticket --
thanks for pointing that out.

Wyatt

Lori Cho

unread,
Oct 2, 2015, 10:40:16 AM10/2/15
to Wyatt Alt, puppet...@googlegroups.com
I was reading release notes. PuppetDB 3.x ou works with Puppet 4?

Wyatt Alt

unread,
Oct 2, 2015, 1:59:48 PM10/2/15
to Lori Cho, puppet...@googlegroups.com
PuppetDB 3.x and PuppetDB 2.x both work with Puppet 4. PuppetDB 3.x does not work with Puppet 3.

Wyatt
Reply all
Reply to author
Forward
0 new messages