-
Notifications
You must be signed in to change notification settings - Fork 3.3k
receiver/postgresql - Fixing the field name client_addr in query_sample collection #42446
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
Conversation
|
@sv-splunk If this PR is ready for review, can you move it from the draft? That way, we can get codeowners to review it. |
|
Hi @VihasMakwana this PR is now ready for review. Thanks |
|
@sv-splunk it looks like the action failed because of a blip with the golang proxy, do you mind force pushing another commit to trigger a rerun? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this file got included accidentally
|
@crobert-1 could you please help review and merge this PR please? Thanks |
Co-authored-by: Curtis Robert <crobert@splunk.com>
|
@crobert-1 if you could also merge please ( checks passed )? Thanks |
I don't have permission to merge. I've added the |
|
Thank you for your contribution @sv-splunk! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey. |
Description
In the field mapping of query_sample attributes in client.go, we are currently mapping `currentAttributes["network.peer.address"] = row["client_addrs"], and in this line client_addrs is misspelled. Actual field name in pg_stat_activity table is client_addr.
Link to tracking issue
Fixes #42447
Testing
Documentation