Jira (PUP-6350) Include last_transaction_uuid if exists, in a report to aid in timelining for PDB and its ilk
Title: Message Title Kenneth Barber commented on PUP-6350 Re: Include last_transaction_uuid if exists, in a report to aid in timelining for PDB and its ilk Since our plans have been diverted from this, I'm closing it for now. If we need it again, we'll re-open or make a new ticket. 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-6350) Include last_transaction_uuid if exists, in a report to aid in timelining for PDB and its ilk
Title: Message Title Steve Quin updated an issue Puppet / PUP-6350 Include last_transaction_uuid if exists, in a report to aid in timelining for PDB and its ilk Change By: Steve Quin Sprint: CR 2016-06-15, CR 2016-06-29 , CR 2016-07-13 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-6350) Include last_transaction_uuid if exists, in a report to aid in timelining for PDB and its ilk
Title: Message Title Steve Quin updated an issue Puppet / PUP-6350 Include last_transaction_uuid if exists, in a report to aid in timelining for PDB and its ilk Change By: Steve Quin Sprint: CR 2016-06-15 , CR 2016-06-29 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-6350) Include last_transaction_uuid if exists, in a report to aid in timelining for PDB and its ilk
Title: Message Title Kenneth Barber created an issue Puppet / PUP-6350 Include last_transaction_uuid if exists, in a report to aid in timelining for PDB and its ilk Issue Type: New Feature Assignee: Unassigned Created: 2016/05/24 4:36 AM Priority: Normal Reporter: Kenneth Barber We're still investigating the absolute need for this, but its come up that having the previous transaction_uuid while submitting a report can help with understanding gaps in the reports upon reception by PuppetDB. This is useful for eliding understanding around current/last report related events as part of the Change Reporting project/epic. Some of our new work involves figuring out when things went weird between last/current reports & catalogs and guessing for the user what might have happened. This ticket/proposal involves grabbing the last_transaction_uuid from the last transmitted report (if it exists) and stuffing it into the new report during transaction or some other suitable time. Not sure if this is the best implementation, but something like that will do. Also, we're not sure if this is something that should be done in core or not. We can probably do it in our termini, absolute worst case. Add Comment
