Jira (PDB-3092) Improve performance of resource_events queries with 'corrective_change = true
Title: Message Title Karel Brezina assigned an issue to Steve Quin PuppetDB / PDB-3092 Improve performance of resource_events queries with 'corrective_change = true Change By: Karel Brezina Assignee: Steve Quin Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3095) [QA]
Title: Message Title Karel Brezina created an issue PuppetDB / PDB-3095 [QA] Issue Type: Sub-task Assignee: qa Components: PuppetDB Created: 2016/10/11 4:52 AM Priority: Normal Reporter: Karel Brezina Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group
Jira (PDB-3094) Implement
Title: Message Title Karel Brezina created an issue PuppetDB / PDB-3094 Implement Issue Type: Sub-task Assignee: Karel Brezina Components: PuppetDB Created: 2016/10/11 4:51 AM Priority: Normal Reporter: Karel Brezina Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe
Jira (PDB-3092) Improve performance of resource_events queries with 'corrective_change = true
Title: Message Title Karel Brezina commented on PDB-3092 Re: Improve performance of resource_events queries with 'corrective_change = true A partial index like CREATE INDEX resource_events_status_for_corrective_change_idx ON resource_events (status) WHERE corrective_change; would increase performance of queries with corrective_change = true and wouldn't consume a lot of disk space Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For
Jira (PDB-3050) Implementation
Title: Message Title Karel Brezina commented on PDB-3050 Re: Implementation Ryan Senior This is just a sub-task. The main task PDB-3047 contains a bit more description with a link to the main task PE-17254. The main task has more info and a link to UX wireframes. There's even a confluence page - https://confluence.puppetlabs.com/display/enterprise/Report+on+corrective+change+events+in+the+GUI Basically, we need to differentiate between intentional and corrective changes in PE Events. To support that, we had to change aggregate-event-counts and event-counts PDB endpoints to provide intentional and corrective counts for successes (changes) and noops. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3050) Implementation
Title: Message Title Karel Brezina assigned an issue to qa PuppetDB / PDB-3050 Implementation Change By: Karel Brezina Status: Ready for CI Test Assignee: Karel Brezina qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3050) Implementation
Title: Message Title Karel Brezina created an issue PuppetDB / PDB-3050 Implementation Issue Type: Sub-task Assignee: Karel Brezina Components: PuppetDB Created: 2016/09/13 3:29 AM Priority: Normal Reporter: Karel Brezina Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Karel Brezina updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Karel Brezina Sprint: CR SCR 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Karel Brezina updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Karel Brezina Story Points: 5 Sprint: CR 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Karel Brezina assigned an issue to Karel Brezina PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Karel Brezina Assignee: Karel Brezina Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6369) Add new noop_status field to puppet report
Title: Message Title Karel Brezina assigned an issue to qa Puppet / PUP-6369 Add new noop_status field to puppet report Change By: Karel Brezina Status: Ready for CI Test Assignee: Karel Brezina qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Karel Brezina commented on PUP-3042 Re: If a catalog has a dependency cycle, it does not count as failed ping Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Karel Brezina commented on PUP-3042 Re: If a catalog has a dependency cycle, it does not count as failed I reopened this ticket and closed PE-5396 because the problem needs to be solved in Puppet. PE-5396 still contains some valuable comments. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2753) Use noop_pending flag from puppet agent report
Title: Message Title Karel Brezina assigned an issue to Wyatt Alt PuppetDB / PDB-2753 Use noop_pending flag from puppet agent report Change By: Karel Brezina Assignee: Karel Brezina Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2753) Use noop_pending flag from puppet agent report
Title: Message Title Karel Brezina assigned an issue to Karel Brezina PuppetDB / PDB-2753 Use noop_pending flag from puppet agent report Change By: Karel Brezina Assignee: Karel Brezina Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2753) Use noop_pending flag from puppet agent report
Title: Message Title Karel Brezina commented on PDB-2753 Re: Use noop_pending flag from puppet agent report Kenneth Barber Susan McNerney I've updated the description to reflect the implementation in puppet core. The puppet core dependency has been merged. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2753) Use noop_pending flag from puppet agent report
Title: Message Title Karel Brezina updated an issue PuppetDB / PDB-2753 Use noop_pending flag from puppet agent report Change By: Karel Brezina The field reflects result of flag indicates that the report contains noop puppet run.Possible values:- "changed" resource events ( noop run + out- i.e. there are changes that we decided not to apply because of -sync),- "unchanged" ( noop run + in-sync ) ,- "failed" (noop run + failure),- nil (enforcement puppet run) . This field flag needs to be queryable from both reports and nodes entity. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2753) Use noop_pending flag from puppet agent report
Title: Message Title Karel Brezina updated an issue PuppetDB / PDB-2753 Use noop_pending flag from puppet agent report Change By: Karel Brezina Summary: Use noop_status field noop_pending flag from puppet agent report Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6294) Add a proper 'noop' status to the report output
Title: Message Title Karel Brezina commented on PUP-6294 Re: Add a proper 'noop' status to the report output John Duarte I agree. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6294) Add a proper 'noop' status to the report output
Title: Message Title Karel Brezina commented on PUP-6294 Re: Add a proper 'noop' status to the report output John Duarte Ideally, we would test the whole end-to-end scenario once even PUP-6369 and PDB-2753 are implemented. ping Andrew Hayes Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2753) Use noop_status field from puppet agent report
Title: Message Title Karel Brezina created an issue PuppetDB / PDB-2753 Use noop_status field from puppet agent report Issue Type: New Feature Assignee: Unassigned Created: 2016/05/27 9:27 AM Labels: SystemInsights-Dep Priority: Normal Reporter: Karel Brezina The field reflects result of noop puppet run. Possible values: "changed" (noop run + out-of-sync), "unchanged" (noop run + in-sync), "failed" (noop run + failure), nil (enforcement puppet run). This field needs to be queryable from both reports and nodes entity.
Jira (PDB-2495) Use real 'noop' status from puppet agent report, when it has the feature to do this
Title: Message Title Karel Brezina updated an issue PuppetDB / PDB-2495 Use real 'noop' status from puppet agent report, when it has the feature to do this Change By: Karel Brezina Labels: SystemInsights-Dep Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6369) Add new noop_status field to puppet report
Title: Message Title Karel Brezina commented on PUP-6369 Re: Add new noop_status field to puppet report ping Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6369) Add new noop_status field to puppet report
Title: Message Title Karel Brezina created an issue Puppet / PUP-6369 Add new noop_status field to puppet report Issue Type: New Feature Assignee: Unassigned Created: 2016/05/27 8:51 AM Labels: SystemInsights-Dep noop Priority: Normal Reporter: Karel Brezina The field will reflect result of noop puppet run. Possible values: "changed" (noop run + out-of-sync), "unchanged" (noop run + in-sync), "failed" (noop run + failure), nil (enforcement puppet run).
Jira (PUP-6369) Add new noop_status field to puppet report
Title: Message Title Karel Brezina assigned an issue to Karel Brezina Puppet / PUP-6369 Add new noop_status field to puppet report Change By: Karel Brezina Assignee: Karel Brezina Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6294) Add a proper 'noop' status to the report output
Title: Message Title Karel Brezina assigned an issue to Karel Brezina Puppet / PUP-6294 Add a proper 'noop' status to the report output Change By: Karel Brezina Assignee: Karel Brezina Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6294) Add a proper 'noop' status to the report output
Title: Message Title Karel Brezina commented on PUP-6294 Re: Add a proper 'noop' status to the report output Suggested implementation is in https://github.com/puppetlabs/puppet/pull/4986 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6294) Add a proper 'noop' status to the report output
Title: Message Title Karel Brezina commented on PUP-6294 Re: Add a proper 'noop' status to the report output Kylo Ginsberg, Henrik Lindberg, Scott Walker Apart from the indication of "--noop" run, SI team (formerly CM team) needs to know even status of the noop run. In CM Dashboard, we name the noop statuses: "would have failed", "would have changes", "would not have changes". AFAIK, puppet provides only status="unchanged" for all noop runs. I can create a new Jira ticket for that. I just wanted to mention it in this ticket since it's relative. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6210) Report overall status should not be noop because of only one noop resource
Title: Message Title Karel Brezina commented on PUP-6210 Re: Report overall status should not be noop because of only one noop resource Verne Lindner Yes, we only read the overall noop flag set on reports entity. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2494) PQL: support for date_trunc() function
Title: Message Title Karel Brezina commented on PDB-2494 Re: PQL: support for date_trunc() function @ken What about the support for date intervals? Currently, the following condition is not supported in PQL: end_time >= "2016-03-01T00:00:00.000Z" and end_time < "2016-03-15T00:00:00.000Z" Should I create a separate issue for that? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2494) PQL: support for aggregations
Title: Message Title
Karel Brezina created an issue
PuppetDB / PDB-2494
PQL: support for aggregations
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2016/03/07 1:43 AM
Priority:
Normal
Reporter:
Karel Brezina
For CM Dashboard, we need to get aggregated counts of report statuses for individual days, hours and minutes. Currently, we are not able to do that using a PQL query. However, it seems that adding support for one DB function (similar to "date_trunc" in PGS) and interval comparisons for dates to would satisfy our needs.
aggregation by days:
reports [date_trunc("day", end_time), status, count()]{ end_time >= "2016-03-01T00:00:00.000Z" and end_time < "2016-03-15T00:00:00.000Z" and nodes{ facts { name = "osfamily" and value = "RedHat"} } group by date_trunc("day", end_time), status}
aggregation by hours:
reports [date_trunc("hour",
Jira (PDB-1967) Include 'noop' flag in 'nodes' endpoint
Title: Message Title Karel Brezina commented on PDB-1967 Re: Include 'noop' flag in 'nodes' endpoint Kenneth Barber Scott Walker IMHO, we should collect all problems/concerns we have on CM side and send them is one email. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1967) Include 'noop' flag in 'nodes' endpoint
Title: Message Title Karel Brezina commented on PDB-1967 Re: Include 'noop' flag in 'nodes' endpoint Kenneth Barber AFAICR, my last comment was written before the PDB + CM meeting. I'm fine with the document aware projection. Once you implement it, the "latest_report_status" and "latest_report_hash" fields that were added to "nodes" endpoint will be redundant. However, I'm not sure if you can still remove them. CM cannot use them now since "noop" is not there. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1977) Add support for multi-queries
Title: Message Title Karel Brezina commented on PDB-1977 Re: Add support for multi-queries Kenneth Barber It's hard to define urgent. I've recorded a video with 4500 nodes - https://drive.google.com/a/puppetlabs.com/file/d/0B7Fpe9nzOKBXY3F3OGRwNVltdTQ/view?usp=sharing . Please, watch the first part - Overview. Loading and navigation between pages is slow. Once, PDB-1967 and PDB-1977 is implemented, the response times should be several times faster. Currently, to be able to display a few nodes for the page and node counts we need to fetch all nodes and the latest reports for all nodes. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1977) Add support for multi-queries
Title: Message Title Karel Brezina commented on PDB-1977 Re: Add support for multi-queries @ken PDB-1967 needs to be fixed first because it can affect this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1967) Include 'noop' flag in 'nodes' endpoint
Title: Message Title Karel Brezina commented on PDB-1967 Re: Include 'noop' flag in 'nodes' endpoint This could be resolved nicely with the new PQL. So, before the new PQL is in place a new temporary "nodes" endpoint in pe-puppetdb-extension could be created. Maybe, the recently added "latest_report_status" and "latest_report_hash" should be just in the temporary endpoint. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1977) Add support for multi-queries
Title: Message Title Karel Brezina created an issue PuppetDB / PDB-1977 Add support for multi-queries Issue Type: New Feature Assignee: Unassigned Created: 2015/09/17 6:46 AM Priority: Normal Reporter: Karel Brezina Overview page in PE displays a paginated list of nodes and counts of nodes in individual statuses. Currently, all nodes have to be fetched to be able to provide the counts and a few nodes for one page. It would be much better to get the counts and the paginated list directly from PDB. For that a multi-query support is needed since these queries need to be executed in a single transaction. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-1977) Add support for multi-queries
Title: Message Title Karel Brezina commented on PDB-1977 Re: Add support for multi-queries Kenneth Barber Right. Currently, nodes are ordered by report_timestamp in descending order. So, it's natural that two subsequent node queries return different list of nodes. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1849) Add filtering to 'state-overview' endpoint
Title: Message Title Karel Brezina commented on PDB-1849 Re: Add filtering to 'state-overview' endpoint Once PDB-1977 is implemented, this task can be implemented with a sequence of PDB queries which would be more appropriate. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1967) Include 'noop' flag in 'nodes' endpoint
Title: Message Title Karel Brezina commented on PDB-1967 Re: Include 'noop' flag in 'nodes' endpoint As discussed with Ryan Senior, there could be a better approach how to achieve it. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1967) Include 'noop' flag in 'nodes' endpoint
Title: Message Title Karel Brezina created an issue PuppetDB / PDB-1967 Include 'noop' flag in 'nodes' endpoint Issue Type: New Feature Assignee: Unassigned Created: 2015/09/16 10:03 AM Priority: Normal Reporter: Karel Brezina In PE, 'no-op' run status for nodes needs to be distinguished. That's why we need to associate the "noop" flag from the latest report with the corresponding node. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-1820) Include 'status' field in 'nodes' endpoint
Title: Message Title Karel Brezina commented on PDB-1820 Re: Include 'status' field in 'nodes' endpoint 'run status' can contain the following values: changed, failed, noop, unchanged - based on the latest report status unreported - when no report exists unresponsive - when no report has arrived within a given time period Similarly, as in https://github.com/puppetlabs/pe-puppetdb-extensions/blob/master/documentation/api/pe/v1/state-overview.markdown. The endpoint should support: pagination by limit offset parameters filtering on facts and status sorting Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more
Jira (PDB-1849) Add filtering to 'state-overview' endpoint
Title: Message Title Karel Brezina created an issue PuppetDB / PDB-1849 Add filtering to 'state-overview' endpoint Issue Type: New Feature Assignee: Unassigned Created: 2015/08/04 9:07 AM Priority: Normal Reporter: Karel Brezina Add support for filtering by facts to '/pdb/ext/v1/state-overview' endpoint. State Overview (PE Console) displays number of nodes in each status category. When a fact filter is applied it displays number of nodes in each category that match the fact filter. That's why the filtering by facts in state-overview is needed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PDB-1618) SO - unresponsive state is not handled properly
Title: Message Title Karel Brezina created an issue PuppetDB / PDB-1618 SO - unresponsive state is not handled properly Issue Type: Bug Assignee: Unassigned Created: 2015/06/16 1:32 AM Priority: Normal Reporter: Karel Brezina There seem to be several problems: unresponsive threshold should be in line for both /state-counts and /nodes endpoints otherwise the numbers in the header show something different than the rows below. See PDB ext doc how to add the missing parameter to the aggregate query. it's not possible to change the unresponsive threshold even for the /nodes endpoint. In fact, PDB default (3600) is always used. The problem is [https://github.com/puppetlabs/pe-console-middleware/blob/master/src/puppetlabs/pe_console_middleware/cm/state_overview/core.clj#L92|here] and here. (str no-report-cutoff-time) needs to be used instead of just no-report-cutoff-time since no-report-cutoff-time is an object that cannot be JSONificated or is JSONified incorrectly. PDB doesn't understand it and uses its default. Add
Jira (PDB-1472) [Performance] Improvements for paged results
Title: Message Title Karel Brezina commented on PDB-1472 Re: [Performance] Improvements for paged results Thanks Wyatt Alt for taking your time. I'm glad that you found the strange behavior even on your machine. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1472) [Performance] Improvements for paged results
Title: Message Title Karel Brezina commented on PDB-1472 Re: [Performance] Improvements for paged results Wyatt Alt That's weird. I'm also on PGS 9.4.0. I did run vacuum analyze. Current query: https://gist.github.com/kbrezina/7e702f65a926b2254998 Proposed query: https://gist.github.com/kbrezina/e5af5313761dc96de4cf My observations: totally different query plans for the current query the same query plan for the proposed query the query plan for the proposed query doesn't use the end_time index - proposed query with added '(end_time, id)' index: https://gist.github.com/kbrezina/47341a9aeb25420c when I decrease offset to 100,000 then my query plan for the current query is the same as yours: https://gist.github.com/kbrezina/9344f8dfd3e7539b4ee6 It seems that your PGS is installed on a more powerful machine. Could that matter? My results are from VM Ubuntu 14.04 with 4 GB RAM and 2 CPUs. However, similar results are from my workstation OSX 10.10.3 with 16 GB RAM and 4 CPUs. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 post to this group, send email to
Jira (PDB-1472) [Performance] Improvements for paged results
Title: Message Title Karel Brezina created an issue PuppetDB / PDB-1472 [Performance] Improvements for paged results Issue Type: Improvement Assignee: Unassigned Created: 2015/05/04 5:33 AM Priority: Normal Reporter: Karel Brezina The original PuppetDB query for paged results is suboptimal with huge offsets. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1472) [Performance] Improvements for paged results
Title: Message Title Karel Brezina commented on PDB-1472 Re: [Performance] Improvements for paged results For paged reports PuppetDB uses the following query: SELECT paged_results.* FROM ( SELECT reports.certname AS certname, reports.configuration_version AS configuration_version, reports.end_time AS end_time, environments.name AS environment, reports.hash AS hash, reports.metrics AS metrics, reports.receive_time AS receive_time, report_statuses.status AS status FROM reports LEFT JOIN environments ON environments.id = reports.environment_id LEFT JOIN report_statuses ON reports.status_id = report_statuses.id) paged_results
Jira (PDB-1472) [Performance] Improvements for paged results
Title: Message Title Karel Brezina commented on PDB-1472 Re: [Performance] Improvements for paged results PG dump of my DB is here. To load the data to puppetdb database use: gunzip -c puppetdb.gz | psql puppetdb Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1459) Support extract with no subexpression
Title: Message Title Karel Brezina commented on PDB-1459 Re: Support extract with no subexpression Ryan Senior It seems that the subexpression can be empty: [extract, [foo,bar] null] or [extract, [foo,bar] []] I'm not sure if it's the proper approach though. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For
