Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define and document enhancedDbReporting #31

Open
dyladan opened this issue May 14, 2020 · 3 comments
Open

Define and document enhancedDbReporting #31

dyladan opened this issue May 14, 2020 · 3 comments

Comments

@dyladan
Copy link
Member

dyladan commented May 14, 2020

I think that's a great idea. Would also be nice to decide and document exactly what "enhanced" db reporting means so all plugins can be consistent.

Originally posted by @dyladan in open-telemetry/opentelemetry-js#1044 (comment)

Would be nice if we could make this flag consistent across all plugins.

@vmarchaud
Copy link
Member

@dyladan What did you imagine for this ? With instrumentation we have now a working autocomplete on configuration and its documented in README of instrumentations that support it

@github-actions
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@dyladan
Copy link
Member Author

dyladan commented Apr 12, 2022

@vmarchaud nothing in particular. Some db instrumentations support this boolean config and it's not documented anywhere consistently what it means. So you may get different "enhanced" reporting from pg and from mysql

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants