Consider OTel Metrics

[leastprivilege]

https://opentelemetry.io/docs/reference/specification/metrics/

[josephdecock]

Is this a duplicate of #1199?

[leastprivilege]

yes. thanks!

[leastprivilege]

YouTube video: https://youtu.be/c4AJlZeX2fE

MS implementation: dotnet/aspnetcore#46834

[brockallen]

Perhaps relevant? dotnet/core#8437 (comment)

[leastprivilege]

Recap:

• We pick a first round of useful metrics and define them in IdentityServer
• We discuss separate metrics vs metrics with tags/properties
• We emit the metrics from within the core engine
• Maybe we need to have metrics in the QS UI (e.g. login success/failure)

@AndersAbel sounds good?

[AndersAbel]

@leastprivilege Yes, looks good. First step will be to create the list of useful metrics and discuss.

[mrjamiebowman]

Just wanted to reach out and tell you guys that you're doing a wonderful job with this.

Open Telemetry is the future, we have been experimenting with this and Identity Server 6 and it has made troubleshooting performance issues significantly easier.

I saw the incoming pull request for adding Meters/Metric Counters around events like token creation, failures. That is amazing! We love that you all are doing this because we want to be able to create alerts and rules if those metrics drop below a threshold or go over. This is wonderful and I look forward to seeing this in IDS 7.

[AndersAbel]

@mrjamiebowman Thank you for your kind words. If you have any suggestions for events that are important to consider for the first round of metrics, please feel free to share them here. Any other opinions on how to design the metrics setup based on your experience are useful too.