Skip to content

Conversation

@zhiyuanliang-ms
Copy link
Member

@zhiyuanliang-ms zhiyuanliang-ms commented Jul 26, 2024

Why this PR?

#583

We want to know these things.

  1. How many configuration stores have load balancing enabled
  2. How many application startups were saved by failing over
  3. How many refresh operations were saved by failing over

Replica auto discovery is enabled by default. So we don't track it.

The request type (startup/refresh) is already added to the request tracing. So as long as we add tag for the request if it is a failover request, we can tell whether it saved startup or refresh operation.

Visible change

Correlation context will have two more tags: UsesLoadBalancing and FailoverRequest

@zhiyuanliang-ms zhiyuanliang-ms changed the title Add failover telemetry Add failover & load balancing telemetry Aug 5, 2024
@RichardChen820
Copy link
Member

LGTM

@zhiyuanliang-ms zhiyuanliang-ms force-pushed the zhiyuanliang/failover-telemetry branch from 69d27d6 to fada45a Compare August 14, 2024 07:00
@zhiyuanliang-ms zhiyuanliang-ms force-pushed the zhiyuanliang/failover-telemetry branch from fada45a to 7a5fcfa Compare August 14, 2024 07:00
@zhiyuanliang-ms zhiyuanliang-ms force-pushed the zhiyuanliang/failover-telemetry branch from 2cb2e34 to d730fd6 Compare August 15, 2024 06:26
@zhiyuanliang-ms zhiyuanliang-ms merged commit d551536 into preview Aug 20, 2024
@zhiyuanliang-ms zhiyuanliang-ms deleted the zhiyuanliang/failover-telemetry branch August 20, 2024 06:41
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.

7 participants