Skip to content

[improve][pip] PIP-471: Authorization operation metrics#25513

Open
mattisonchao wants to merge 3 commits intomasterfrom
mattison/pip-298-authorization-metrics
Open

[improve][pip] PIP-471: Authorization operation metrics#25513
mattisonchao wants to merge 3 commits intomasterfrom
mattison/pip-298-authorization-metrics

Conversation

@mattisonchao
Copy link
Copy Markdown
Member

@mattisonchao mattisonchao commented Apr 13, 2026

Motivation

Pulsar lacks a generic broker authorization metric model that can be used for alerting, dashboards, and compliance-oriented monitoring. This PIP proposes low-cardinality authorization operation metrics with success, failure, and error results for both Prometheus and OpenTelemetry.

Modifications

  • Add pip/pip-471.md for authorization operation metrics.
  • Document the Prometheus metric pulsar_authorization_operations_total.
  • Document the OpenTelemetry metric pulsar.authorization.operation.count and its bounded attributes.
  • Document result="error" for authorization evaluation errors before an allow/deny decision is returned.

Testing

  • git diff --check

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

@github-actions github-actions Bot added the PIP label Apr 13, 2026
@mattisonchao mattisonchao changed the title Add PIP-466 for authorization operation metrics [improve][pip] PIP-466: Authorization operation metrics Apr 13, 2026
@merlimat
Copy link
Copy Markdown
Contributor

It should be PIP-468

@mattisonchao mattisonchao force-pushed the mattison/pip-298-authorization-metrics branch from 0703dbd to c160138 Compare April 26, 2026 03:29
@mattisonchao mattisonchao changed the title [improve][pip] PIP-466: Authorization operation metrics [improve][pip] PIP-471: Authorization operation metrics Apr 26, 2026
@mattisonchao
Copy link
Copy Markdown
Member Author

Renumbered this proposal to PIP-471. PIP-466, PIP-467, and PIP-468 are now on master, and PIP-469/PIP-470 are already used by open PIP PRs.

@mattisonchao mattisonchao self-assigned this Apr 26, 2026
Comment thread pip/pip-471.md
Comment on lines +192 to +193
| `success` | The authorization request was allowed. |
| `failure` | The authorization request was denied or rejected by authorization handling. |
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Since this metric label represents an authorization outcome, could we use allowed/denied instead of success/failure? The explicit values will read more clearly in dashboards and PromQL queries, and avoid ambiguity about what success means here (policy evaluated successfully vs. access granted).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants