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

FFM-10924 Streaming disconnect log level changes #125

Merged
merged 4 commits into from
Apr 15, 2024
Merged

Conversation

erdirowlands
Copy link
Contributor

@erdirowlands erdirowlands commented Apr 15, 2024

What

  • Now logs stream disconnect & timeouts as debug instead of error
  • An error will be logged if reconnection is still being attempted after every 5, 10, 15... attempts

Why

We expect occasional stream disconnects/timeouts and the SDK will "self-heal" by reconnecting. Logging these as errors in the first instance is misleading and can cause users to be concerned unjustifiably.

Testing

Manual - using proxy tool to simulate disconnects.

Copy link
Contributor

@knagurski knagurski left a comment

Choose a reason for hiding this comment

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

Just one minor thing with formatting and remember to update all the examples using npm run install-examples

erdirowlands and others added 2 commits April 15, 2024 14:49
Co-authored-by: Kevin Nagurski <Kevin.nagurski@harness.io>
@erdirowlands erdirowlands merged commit f98a442 into main Apr 15, 2024
3 checks passed
@erdirowlands erdirowlands deleted the FFM-10924 branch April 15, 2024 14:05
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.

3 participants