knative/eventing

Add metrics for OIDC

Open

#7,877 opened on Apr 26, 2024

View on GitHub
 (1 comment) (0 reactions) (1 assignee)Go (632 forks)auto 404
help wantedtriage/accepted

Repository metrics

Stars
 (1,551 stars)
PR merge metrics
 (PR metrics pending)

Description

As the Eventing OIDC feature track describes, cluster administrators and developers should be able to see the following metrics for a particular resource:

  • Number of unauthenticated requests (these requests will get a 401 status code)
  • Number of requests with an invalid token (these requests will get a 401 status code)

In addition, event senders (Triggers, Subscriptions, Sources) should record the following metrics:

  • Whether or not the event was delivered with an identity
  • How often an identity was fetched (vs used from a cache) and any errors fetching tokens

Contributor guide

Research direction
Study the OIDC feature track document for metrics requirements, then implement the metrics using OpenTelemetry in the Knative Eventing codebase, focusing on request authentication and identity fetching.
Tech stack
go
Domain
backendsecurityapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetesOIDC
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40