[PDB-653] Certain metrics aren't getting updated Created: 2014/05/06  Updated: 2016/04/27  Resolved: 2014/09/16

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: PDB 2.0.0
Fix Version/s: PDB 2.2.1

Type: Bug Priority: Normal
Reporter: Daniele Sluijters Assignee: Wyatt Alt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2014-05-06 at 17.54.39.png     PNG File Screen Shot 2014-05-07 at 15.36.15.png    
Issue Links:
Duplicate
is duplicated by PDB-124 PuppetDB Dashboard returns a ? on DLO... Closed
Template:
Story Points: 1
Sprint: 20140507 to 20140521, 20140827 to 20140910, PuppetDB 2014-09-24

 Description   

In RC1 the Collection Queries, DLO Compression, DLO size on disk and Discarded Messages are all stuk on a ?.

I would expect at least Collection Queries to show some output as they should be happening with exported resources in our catalogs. I'd also expect API queries done by Puppetboard to influence that number.



 Comments   
Comment by Daniele Sluijters [ 2014/05/06 ]

Just like PDB-652 it took a while but Collection Queries is now showing numbers, the rest of the metrics is still at a ?.

Comment by Ken Barber [ 2014/05/06 ]

So:

  • DLO compression is transient, it only gets calculated after a reject and after compression
  • The DLO size on disk, should not be transient, however ... it seems to me looking at dlo.clj, that this stuff only gets calculated on a failure. So while the data is correct and isn't just "in ram" it doesn't get populated until the first failure is seen after startup.

I think point #2 is a bug, at least but we should dig into #1 as well as I might have missed something.

This has been the behaviour for a while as well, but I'm leaving this ticket as it stands. I think its a valid bug, but not a release blocker.

Comment by Ken Barber [ 2014/05/07 ]

Added some screenshots to confirm my assumptions - indeed the DLO size on disk and discarded messages are not updated until the first fault seen since startup.

The first screenshot shows these as ? before failure, second screenshot shows the results immediately after failure.

Generated at Thu Nov 14 13:17:38 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.