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

feat: include endpoint in grpc logs #3362

Merged

Conversation

sk-
Copy link
Contributor

@sk- sk- commented Jun 28, 2023

Description

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 and error messages. That would allow us to better debug the issue and rule out faulty parts in our systems.

Type of change

  • New feature (non-breaking change which adds functionality)

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/ or opentelemetry-sdk/

  • The method interfaces of test/util have changed

  • Scripts in scripts/ that were copied over to the Contrib repo have changed

  • Configuration 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 added

  • Major changes to project information, such as in:

    • README.md
    • CONTRIBUTING.md
  • Yes. - Link to PR:

  • No.

Checklist:

  • Followed the style guidelines of this project
  • Changelogs have been updated
  • Unit tests have been added
  • Documentation has been updated

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- sk- requested a review from a team as a code owner June 28, 2023 16:16
@sk- sk- changed the title feat: incluse endpoint in grpc transient error warning feat: include endpoint in grpc transient error warning Jun 28, 2023
@sk- sk- changed the title feat: include endpoint in grpc transient error warning feat: include endpoint in grpc logs Jun 28, 2023
@sk- sk- requested a review from pmcollins June 29, 2023 15:11
Copy link
Member

@pmcollins pmcollins left a 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.

@sk-
Copy link
Contributor Author

sk- commented Jun 30, 2023

@aabmass who should I ask for a review on behalf of the python approvers?

@ocelotl ocelotl enabled auto-merge (squash) July 5, 2023 10:32
@ocelotl ocelotl merged commit 570d27e into open-telemetry:main Jul 5, 2023
111 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants