Release v1.7.2

Overview

This patch release focuses on fixing critical issues with OpenTelemetry integration and metrics collection, improving the reliability and accuracy of monitoring capabilities.

🐛 Bug Fixes

OpenTelemetry & Batch Processing

• Fixed OpenTelemetry integration and batch implementation issues - Resolved compatibility problems and improved batch processing reliability
  • PR: #21
  • Author: @amirsalarsafaei

Metrics Configuration

• Corrected metric bucket configuration - Fixed histogram bucket settings to provide more accurate performance metrics
  • PR: #22
  • Author: @amirsalarsafaei

Full Changelog: v1.7.1...v1.7.2

Release v1.7.1

Changes:

• Fixed poolstatus interface issue
• Added examples docker compose for e2e testing and usage sample.

Full Changelog: v1.7.0...v1.7.1

Release v1.7.0

v1.7.0

Added

• Connection Pool Monitoring & Tracing: The library now instruments pgxpool connection handling to provide deeper visibility into pool performance.
  • A new trace span is created for the time spent waiting to acquire a connection from the pool. This helps identify and debug connection pool contention.
  • New counters track the total number of connections acquired and released, allowing you to monitor pool usage and detect potential connection leaks.
  • Open Telemetry compliant pool status collection. Stats like connection usages, max connections and etc.
• Query Name Suffix in Span Name

Full Changelog: https://github.com/amirsalarsafaei/sqlc-pgx-monitoring/compare/v1.6.0...v1.7.0

Release v1.6.0

What's Changed

🐛 Bug Fixes & Improvements

• Fixed span kind configuration: Corrected OpenTelemetry span kind to use CLIENT instead of the default, ensuring proper trace categorization for database operations
• Enhanced testing infrastructure: Refactored test suite with improved mocks and test coverage for better reliability

🔗 Pull Requests

• Use span kind client & refactor tests and mocks by @amirsalarsafaei in #16

🙏 Acknowledgments

• Thanks to @johnlemon93 for reporting the span kind issue in #15

Full Changelog: v1.5.1...v1.6.0

v1.5.1

Release v1.5.1

🐛 Bug Fixes

• Logging: Fixed log level inconsistency by @amirsalarsafaei in #14 reported by @ali-mohit

📝 Details

This release resolves the log level issue introduced in #12. The logging behavior has been corrected so that:

• Error conditions are now properly logged at error level
• Non-error messages are logged at info level

This ensures consistent and appropriate log severity levels throughout the application.

---

Full Changelog: v1.5.0...v1.5.1

Release v1.5.0

What's Changed

• Fix WithShouldLog behavior to execute ShouldLog function for all queries by @nekorro in #12

New Contributors

• @nekorro made their first contribution in #12

Full Changelog: v1.4.0...v1.5.0

Release 1.4.0

In this release the project was aligned with OpenTelemetry's Database monitoring attribute conventions defined here

Release v1.3.1

Bug Fixes

• fixed WithLogger not working in #9 by @amirsalarsafaei . reported by @sonalys

Maintenance

• added logger tests

Release v1.3.0

🚨 Release v1.3.0 - Breaking Changes

⚠️ Important Notice

Unfortunately, we had to revise the library's signature, which introduces breaking changes. Code written for v1.2.x will need to be updated to work with this version.

Note: While these are breaking changes, we're not moving to v2.0 due to Go module versioning complexity.

✨ New Features & Improvements

Observability

• 📊 Added OpenTelemetry support
  • Distributed tracing
  • Metrics collection
  • Enhanced trace and metric attributes
• 📝 Integrated Go's standard structured logging (slog)

Technical Enhancements

• ⚡ Multiple configuration options for finer control
• 🔄 Upgraded to Go 1.23
• ✅ Improved test coverage (82%)

📝 Additional Notes

For detailed documentation and examples, please visit our Readme.

Feel free to open an issue if you encounter any problems or have questions!

Release v1.2

bug fixes:

• fixed the status label appearing success on error queries

improvements:

• now using official Logrus logger
• added option for should log
• added query name in logs for better Sentry logs.

There are some breaking changes, be aware.