Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres
Title: Message Title Claudia Petty updated an issue PuppetDB / PDB-4875 Add option to log PDBQuery correlation uuids in Postgres Change By: Claudia Petty Labels: jira_escalated 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.370904.1598994706000.2243.1687359366934%40Atlassian.JIRA.
Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres
Title: Message Title Alvin Rodis updated an issue PuppetDB / PDB-4875 Add option to log PDBQuery correlation uuids in Postgres Change By: Alvin Rodis Labels: jira_escalated Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.370904.1598994706000.29145.1652454900149%40Atlassian.JIRA.
Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres
Title: Message Title Alvin Rodis updated an issue PuppetDB / PDB-4875 Add option to log PDBQuery correlation uuids in Postgres Change By: Alvin Rodis Zendesk Ticket Count: 1 Zendesk Ticket IDs: 48171 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.370904.1598994706000.29144.1652454900100%40Atlassian.JIRA.
Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres
Title: Message Title David McTavish updated an issue PuppetDB / PDB-4875 Add option to log PDBQuery correlation uuids in Postgres Change By: David McTavish Priority: Normal Low Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.370904.1598994706000.13416.1644506760135%40Atlassian.JIRA.
Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres
Title: Message Title David McTavish assigned an issue to Rob Browning PuppetDB / PDB-4875 Add option to log PDBQuery correlation uuids in Postgres Change By: David McTavish Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.370904.1598994706000.19716.1642024200245%40Atlassian.JIRA.
Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres
Title: Message Title David McTavish commented on PDB-4875 Re: Add option to log PDBQuery correlation uuids in Postgres rob.browning is this a dupe of PDB-4849 ? if so, can you close please Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.370904.1598994706000.19715.1642024200201%40Atlassian.JIRA.
Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4875 Add option to log PDBQuery correlation uuids in Postgres Change By: Zachary Kent - In PDB-4834 we added a log-queries config option which logs the AST & SQL produced as a result of queries PDB receives. It may be useful to have a way to correlate these logs with those in Postgres. One way of accomplishing this would be to have Postgres log the PDB uuid used for a query. Then using the Postgres log line prefix created by %c we could more easily correlate any logging on the Postgres side with those generated in PDB. - - [Read here|https://www.postgresql.org/docs/11/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT] for more background on log_line_prefix in postgres. - - In the PDB code we would need to run `select pdb-uuid;` or a similar statement using the same connection as the SQL query to trigger postgres to log the PDB uuid with the %c id Postgres will add as a log line prefix. This would need to happen in [query_eng.clj/stream-query-result|https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/query_eng.clj#L210] and in [query_eng.clj/produce-streaming-body|https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/query_eng.clj#L280]. Notice in the 2nd link how we would need to do this in the inner `with-transacted-connection` form. This is due to PDB currently using two hikari connections per query as explained in PDB-4871. If this ticket is resolved you won't need to worry about the nested transactions using different connections. - Add Comment
Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4875 Add option to log PDBQuery correlation uuids in Postgres Change By: Zachary Kent - In PDB-4834 we added a log-queries config option which logs the AST & SQL produced as a result of queries PDB receives. It may be useful to have a way to correlate these logs with those in Postgres. One way of accomplishing this would be to have Postgres log the PDB uuid used for a query. Then using the Postgres log line prefix created by %c we could more easily correlate any logging on the Postgres side with those generated in PDB. - - [Read here|https://www.postgresql.org/docs/11/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT] for more background on log_line_prefix in postgres. - - In the PDB code we would need to run `select pdb-uuid;` or a similar statement using the same connection as the SQL query to trigger postgres to log the PDB uuid with the %c id Postgres will add as a log line prefix. This would need to happen in [query_eng.clj/stream-query-result|https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/query_eng.clj#L210] and in [query_eng.clj/produce-streaming-body|https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/query_eng.clj#L280]. Notice in the 2nd link how we would need to do this in the inner `with-transacted-connection` form. This is due to PDB currently using two hikari connections per query as explained in PDB-4871. If this ticket is resolved you won't need to worry about the nested transactions using different connections. - Add Comment
Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4875 Add option to log PDBQuery correlation uuids in Postgres Issue Type: New Feature Assignee: Unassigned Created: 2020/09/01 2:11 PM Priority: Normal Reporter: Zachary Kent In PDB-4834 we added a log-queries config option which logs the AST & SQL produced as a result of queries PDB receives. It may be useful to have a way to correlate these logs with those in Postgres. One way of accomplishing this would be to have Postgres log the PDB uuid used for a query. Then using the Postgres log line prefix created by %c we could more easily correlate any logging on the Postgres side with those generated in PDB. Read here for more background on log_line_prefix in postgres. In the PDB code we would need to run `select pdb-uuid;` or a similar statement using the same connection as the SQL query to trigger postgres to log the PDB uuid with the %c id Postgres will add as a log line prefix. This would need to happen in query_eng.clj/stream-query-result and in query_eng.clj/produce-streaming-body. Notice in the 2nd link how we would need to do this in the inner `with-transacted-connection` form. This is due to PDB currently using two hikari connections per query as explained in PDB-4871. If this ticket is resolved you won't need to worry about the nested transactions using different connections. Add Comment
