Skip to content

Trace reconnecting MQTT errors at INFO level#1739

Closed
aalmazanarbs wants to merge 1 commit into
Azure:mainfrom
aalmazanarbs:feature/trace-reconnecting-as-info
Closed

Trace reconnecting MQTT errors at INFO level#1739
aalmazanarbs wants to merge 1 commit into
Azure:mainfrom
aalmazanarbs:feature/trace-reconnecting-as-info

Conversation

@aalmazanarbs
Copy link
Copy Markdown

No description provided.

@aalmazanarbs
Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@timtay-microsoft
Copy link
Copy Markdown
Member

timtay-microsoft commented Sep 12, 2023

I'd rather ask users to opt into this kind of behavior as opposed to making it the default. How about #1740 instead?

timtay-microsoft added a commit that referenced this pull request Sep 18, 2023
… as errors (#1740)

SAS authorized MQTT connections have routine disconnects that some users don't want treated as errors or warnings in logs. This adds a flag they can set in client options to opt out of the current default.

Also defer creating a multiplexing retry policy until a multiplexing client is created to avoid unnecessary logs

Like #1739 but requiring opting in to logging these routine disconnects opt-in
@timtay-microsoft
Copy link
Copy Markdown
Member

Closing this as #1740 addresses this issue

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.

2 participants