-
Notifications
You must be signed in to change notification settings - Fork 658
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
feat: include endpoint in grpc logs #3362
Merged
ocelotl
merged 8 commits into
open-telemetry:main
from
sk-:feat/include_endpoint_grpc_warningwq
Jul 5, 2023
Merged
feat: include endpoint in grpc logs #3362
ocelotl
merged 8 commits into
open-telemetry:main
from
sk-:feat/include_endpoint_grpc_warningwq
Jul 5, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We are getting many transient error warnings in production ``` Transient error <StatusCode.UNAVAILABLE: (14, 'unavailable')> encountered while exporting metrics, retrying in 1s. ``` but unfortunately they don't have enough information to debug the issue, as we have two exporters, one exporting to our internal metric system and another one exporting to Uptrace. In this PR we add the endpoint to the warning. That would allow us to better debug tghe issue and rule out faulty parts ion our systems.
sk-
changed the title
feat: incluse endpoint in grpc transient error warning
feat: include endpoint in grpc transient error warning
Jun 28, 2023
sk-
changed the title
feat: include endpoint in grpc transient error warning
feat: include endpoint in grpc logs
Jun 28, 2023
pmcollins
reviewed
Jun 29, 2023
...pentelemetry-exporter-otlp-proto-grpc/src/opentelemetry/exporter/otlp/proto/grpc/exporter.py
Outdated
Show resolved
Hide resolved
Suggestion from open-telemetry#3362 (comment)
pmcollins
approved these changes
Jun 29, 2023
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.
LGTM, thanks for the enhancement.
@aabmass who should I ask for a review on behalf of the python approvers? |
srikanthccv
approved these changes
Jul 1, 2023
ocelotl
approved these changes
Jul 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We are getting many transient error warnings in production
but unfortunately they don't have enough information to debug the issue, as we have two exporters, one exporting to our internal metric system and another one exporting to Uptrace.
In this PR we add the endpoint to the warning and error messages. That would allow us to better debug the issue and rule out faulty parts in our systems.
Type of change
How Has This Been Tested?
The changes logic was already tested, in this PR we adjust those tests to include the new information.
Does This PR Require a Contrib Repo Change?
Answer the following question based on these examples of changes that would require a Contrib Repo Change:
The OTel specification has changed which prompted this PR to update the method interfaces of
opentelemetry-api/
oropentelemetry-sdk/
The method interfaces of
test/util
have changedScripts in
scripts/
that were copied over to the Contrib repo have changedConfiguration files that were copied over to the Contrib repo have changed (when consistency between repositories is applicable) such as in
pyproject.toml
isort.cfg
.flake8
When a new
.github/CODEOWNER
is addedMajor changes to project information, such as in:
README.md
CONTRIBUTING.md
Yes. - Link to PR:
No.
Checklist: