Investigate AuthN/AuthZ metrics in ASP.NET Core · Issue #47603 · dotnet/aspnetcore (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

Issue #47536 adds metrics for existing counters.

We should investigate where adding new metrics makes sense in ASP.NET Core. Metrics are easier to add and test than old event counters. And tags make them more powerful.

Initial ideas:

• Rate limiting - queue counts
• Routing - match/fallback/no match counts
• AuthN/AuthZ - success/failure counts

AuthZ

• Number of requests that require authz
  • Policy name
  • Result (success/failure)

AuthN

• Challenge count
  • Scheme name
• Authenticated requests count - don't record for result
  • Scheme name
  • Result (success/failure/noop)

Sign in handler

• Sign in count
  • Scheme name

Sign out handler

• Sign out count
  • Scheme name