Skip to content

Bound telemetry algorithm dimension cardinality#3490

Merged
iNinja merged 3 commits into
dev8xfrom
iinglese/bound-telemetry-algorithm-dimension
May 22, 2026
Merged

Bound telemetry algorithm dimension cardinality#3490
iNinja merged 3 commits into
dev8xfrom
iinglese/bound-telemetry-algorithm-dimension

Conversation

@iNinja

@iNinja iNinja commented May 15, 2026

Copy link
Copy Markdown
Contributor

Constrains the algorithm dimension in crypto telemetry to a known allowlist, replacing unbounded user-supplied values with a fixed placeholder. This prevents high-cardinality dimension explosion in telemetry pipelines.

Changes

  • Algorithm values are validated against a known set before being emitted as telemetry dimensions
  • Unknown algorithms are recorded as a constant placeholder value
  • Updated telemetry tests

Map raw algorithm strings to known families (RSA, RSA-PSS, ECDSA, HMAC,
none, other) before emitting as metric dimensions to prevent unbounded
cardinality growth from arbitrary algorithm values.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@iNinja iNinja requested a review from a team as a code owner May 15, 2026 14:21
@adcosta118

Copy link
Copy Markdown

Can's we expose to the developers a fixed enum including unknown, instead relying on them providing arbitrary telemetry labels?

Comment thread src/Microsoft.IdentityModel.Tokens/Telemetry/TelemetryConstants.cs
@iNinja iNinja merged commit 0d6690c into dev8x May 22, 2026
2 checks passed
This was referenced Jun 2, 2026
This was referenced Jun 8, 2026
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.

4 participants