Jira (PDB-5593) Generating report data

[Joshua Partlow (Jira)]

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 ***** 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. 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 (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.13205.1683930480024%40Atlassian.JIRA.