[DB-SIG] Better Database Visibility
Jean-Mark Wright
jmwright at waveapps.com
Thu Sep 12 08:29:38 EDT 2024
Hi,
I'm aiming to improve database trace quality to better understand what's
happening in our database. I'd love to get index information, query
planning information, performance statistics and richer errors into our
database spans. I don't know what the best layer is for this enrichment
(e.g. database module, OpenTelemetry, in our application, etc...).
I'm looking for the following specifically:
- Thoughts on the possibilities of getting this information and where it
would come from?
- Thoughts on whether this enrichment aligns with the database
specification's purpose?
- Any contacts who could help answer or provide more questions.
This article
<https://jaywhy13.hashnode.dev/dear-editor-we-need-better-database-observability>
captures the issues I've faced in greater detail.
Thanks in advance for your help!
--
*JEAN-MARK **WRIGHT* | Staff Engineer
<https://s3.amazonaws.com/wave-buoyant/public/Wave_logo_RGB-109x30.svg>
<https://www.waveapps.com/> <https://www.waveapps.com/>
<https://www.waveapps.com/> <https://www.waveapps.com/>
<https://www.waveapps.com/>
Join our community on Facebook <http://www.facebook.com/waveHQ>, LinkedIn
<http://www.linkedin.com/company/1196866>, or Instagram
<https://www.instagram.com/wave_hq>
This message and any attachments are intended only for the use of the
addressee and should be considered confidential. If you are not an intended
recipient, you may not review, copy or distribute this message. If you have
received this communication in error or would like to stop receiving these
emails, please notify the sender by replying to this email. Wave is located
at 500-155 Queens Quay East, Box 3, Toronto ON, M5A 0W4.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/db-sig/attachments/20240912/e22b7334/attachment.html>
More information about the DB-SIG
mailing list