Jira (PDB-5593) Generating report data
Title: Message Title Claudia Petty updated an issue PuppetDB / PDB-5593 Generating report data Change By: Claudia Petty Labels: new-feature Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481308.1676309116000.2229.1687359366253%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5593 Generating report data Change By: Rob Browning Fix Version/s: PDB 8.0.1 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481308.1676309116000.8946.1686610560030%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow commented on PDB-5593 Re: Generating report data Pez had failed I think due to the openssl issue breaking cast for postgres. Rekicked as that is resolved now, to get this into PE main. Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481308.1676309116000.5173.1686071760023%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Cas Donoghue updated an issue PuppetDB / PDB-5593 Generating report data Change By: Cas Donoghue Sprint: Skeletor 05/24/2023 , Skeletor 06/07/2023 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481308.1676309116000.1912.1684952040098%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob in reports.logs)** variable*** tags array*** message** plugin lines** could have debug lines*** a pe primary report with --debug, for example, adds ~11000 log entries and 5MB to the report.* metrics (stored as a blob in reports.metrics)** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** stored as a blob (reports.resources)** but changed resource properties stored in resource_events*** so each resource events array has one event per resource property change, (file content, owner, mode, for instance would be three events), but typically just one containment_path (corresponds to depth of resource in catalog graph) most variable* old_value* new_value* messageProbably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports. Benchmark varies timestamps, but not events. Also need to think about unchanged resources. Does generate deal with that, or should benchmark mutate reports with that flag on or off? Will add a flag to generate for now. Add Comment This message was sent by Atlassian Jira
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob in reports.logs)** variable*** tags array*** message** plugin lines** could have debug lines* ** a pe primary report with --debug, for example, adds ~11000 log entries and 5MB to the report.* metrics (stored as a blob in reports.metrics)** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** stored as a blob (reports.resources)** but changed resource properties stored in resource_events*** so each resource events array has one event per resource property change, (file content, owner, mode, for instance would be three events), but typically just one containment_path (corresponds to depth of resource in catalog graph) most variable* old_value* new_value* messageProbably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports.Also need to think about unchanged resources. Does generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob in reports.logs )** variable*** tags array*** message** plugin lines** could have debug lines* metrics (stored as a blob in reports.metrics )** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** containment_path stored as a blob ( corresponds to depth of resource in catalog graph reports.resources )** events array ( but changed resource properties stored as in resource_events ) *** most variable old_value new_value message*** so each resource events array has one event per resource property change, (file content, owner, mode, for instance would be three events), but typically just one containment_path (corresponds to depth of resource in catalog graph) most variable* old_value* new_value* message Probably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports.Also need to think about unchanged resources. Does generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob)** variable*** tags array*** message** plugin lines** could have debug lines* metrics (stored as a blob)** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** containment_path (corresponds to depth of resource in catalog graph)** events array (stored as resource_events)*** most variable old_value new_value message*** ever more than 1 one event ? per resource property change, (file content, owner, mode, for instance would be three events), but typically just one Probably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports.Also need to think about unchanged resources. Does generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.481308.1676309116000.12304.1683750060030%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Cas Donoghue updated an issue PuppetDB / PDB-5593 Generating report data Change By: Cas Donoghue Sprint: Skeletor 05/24/2023 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.481308.1676309116000.12281.1683743640131%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob)** variable*** tags array*** message** plugin lines** could have debug lines* metrics (stored as a blob)** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** containment_path (corresponds to depth of resource in catalog graph)** events array (stored as resource_events)*** most variable old_value new_value message*** ever more than 1 event?Probably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports.Also need to think about unchanged resources. So Does generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow - Events * logs (stored as a blob)** variable*** tags array*** message** plugin lines** could have debug lines* metrics (stored as a blob)** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** containment_path (corresponds to depth of resource in catalog graph)** events array (stored as resource_events)*** most variable old_value new_value message*** ever more than 1 event?Probably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports. Also need to think about unchanged resources. So generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5593) Generating report data
Title: Message Title Cas Donoghue commented on PDB-5593 Re: Generating report data Joshua Partlow will work with Austin Blatt to get this filled out with more details. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.481308.1676309116000.4191.1678389420021%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.481308.1676309116000.2412.1677698220128%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5593 Generating report data Issue Type: New Feature Assignee: Unassigned Created: 2023/02/13 9:25 AM Priority: Normal Reporter: Austin Blatt Events per report Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
