Is your feature request related to a problem? Please describe.
When making rolling deployments (i.e. in pod rotations in Kubernetes), we are seeing the following error in our logs:
Hub '{hub}' is now disconnected from '{endpoint}'. Please check log for detailed info.
We're treating logs of Error level as scenarios, where something is really wrong and something that developers needs to pay attention to immediately - and in this case, we don't have any control over the level of this log line because it's set up within ServiceConnectionContainerBase.cs
Ideally, we'd like to have it only as a warning since we know that it does happen when making a rolling deployment.
Describe the solution you'd like
Either:
Simply lowering the _endpointOffline to Warning or
Use a named logger so the consumers are able to control/override the log level using Serilog
Additional context
We've configured Azure SignalR to gracefully shutdown and migrate client connections, like so:
Is your feature request related to a problem? Please describe.
When making rolling deployments (i.e. in pod rotations in Kubernetes), we are seeing the following error in our logs:
Hub '{hub}' is now disconnected from '{endpoint}'. Please check log for detailed info.
We're treating logs of Error level as scenarios, where something is really wrong and something that developers needs to pay attention to immediately - and in this case, we don't have any control over the level of this log line because it's set up within
ServiceConnectionContainerBase.cs
Ideally, we'd like to have it only as a warning since we know that it does happen when making a rolling deployment.
Describe the solution you'd like
Either:
Additional context
We've configured Azure SignalR to gracefully shutdown and migrate client connections, like so:
We're using Serilog to handle the logging for us.