Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Telemetry circuit breaker#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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
saishreeeee wants to merge6 commits intomain
base:main
Choose a base branch
Loading
fromtele-circuit-breaker
Open

Conversation

@saishreeeee
Copy link
Contributor

@saishreeeeesaishreeeee commentedJul 30, 2025
edited
Loading

What type of PR is this?

  • Refactor
  • Feature
  • Bug Fix
  • Other

Description

Circuit breaker in telemetry to prevent server-side overloading using the PyBreaker library

How is this tested?

  • Unit tests
  • E2E Tests
  • Manually
  • N/A

Related Tickets & Documents

PECOBLR-711

Signed-off-by: Sai Shree Pradhan <saishree.pradhan@databricks.com>
@github-actions
Copy link

Thanks for your contribution! To satisfy the DCO policy in ourcontributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

This reverts commita5f46eb.Signed-off-by: Sai Shree Pradhan <saishree.pradhan@databricks.com>
Signed-off-by: Sai Shree Pradhan <saishree.pradhan@databricks.com>
Signed-off-by: Sai Shree Pradhan <saishree.pradhan@databricks.com>
@saishreeeeesaishreeeee marked this pull request as ready for reviewJuly 30, 2025 14:35
@jprakash-db
Copy link
Contributor

jprakash-db commentedJul 30, 2025
edited
Loading

Just confused on why is there even a need for circuit breaker, isn't just handling a good retry mechanism with proper retry behaviour onretry-after time or status code based retry enough? I feel good retry behaviour on TelemetryHttpClient is enough cc@vikrantpuppala

@saishreeeee
Copy link
ContributorAuthor

Just confused on why is there even a need for circuit breaker, isn't just handling a good retry mechanism with proper retry behaviour onretry-after time or status code based retry enough? I feel good retry behaviour on TelemetryHttpClient is enough cc@vikrantpuppala

The retry behaviour is per request, while the circuit breaker works across requests. So if a certain number of requests fail, for a time interval, no request will be sent to the server.

##Requirements

Python 3.8 or above is required.
Python 3.9 or above is required.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

@jprakash-db are we ok with python version upgrades?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This should be ok, given DBT tests pass.

Signed-off-by: Sai Shree Pradhan <saishree.pradhan@databricks.com>
try:
returnself.circuit_breaker.call(self.session.post,url,**kwargs)
exceptCircuitBreakerErrorase:
logger.error("Circuit breaker error: %s",e)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

let's keep all logs pretty much silent for telemetry. use trace instead.

Signed-off-by: Sai Shree Pradhan <saishree.pradhan@databricks.com>
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@vikrantpuppalavikrantpuppalavikrantpuppala left review comments

@samikshya-dbsamikshya-dbsamikshya-db left review comments

@jprakash-dbjprakash-dbAwaiting requested review from jprakash-db

At least 1 approving review is required to merge this pull request.

Assignees

@saishreeeeesaishreeeee

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@saishreeeee@jprakash-db@vikrantpuppala@samikshya-db

[8]ページ先頭

©2009-2025 Movatter.jp