Open Amzani opened 6 months ago
@Amzani
AsyncAPI 3.0x Adoption We can parse the version when a user triggers
asyncapi validate
Right now, the query only provides a raw count of AsyncAPI v3 validations. To get a better understanding of adoption trends, could we calculate the percentage of AsyncAPI v3 validations out of the total validations? This would give us a much clearer picture of v3 adoption over time.
Problem
We aim to provide a dashboard for monitoring our Developer Experience (DX) metrics, which should be collected in https://github.com/asyncapi/community/issues/879
Solution
The dashboard must have the capability to showcase Developer Experience Working group metrics and enable other working groups to add their respective metrics.
Look & Feel
Link to Figma
Where do we get metrics:
This initiative focuses on the CLI metrics
Definition of metrics
Time to first API Design
It's the time between the creation of a new AsyncAPI file and generation (doc, code...) for a specific user.
System errors
Refer to any issue or malfunction of our tools that are not generated by the user (eg. validation errors). Example: https://github.com/asyncapi/cli/issues/1137
Validation errors
Errors from
asyncapi validate
Time to fix a validation error
The delta between a failing validation and successful validation.
Number of created AsyncAPI File
From
asyncapi new file
AsyncAPI 3.0x Adoption
We can parse the version when a user triggers
asyncapi validate
Tech stack
Note: This is a suggestion! anything else relevant with a valid argument can work as well.
Rabbit holes
Assurance in the Metrics Collection:
Rate Limit Consideration for New Relic API:
Scope
Out of bounds
Success criteria