You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a task that was identified in the 10/13 retro:
I ended up spending wasting a lot of time trying to reproduce and determine why the metric-reporter Micronaut rewrite caused the metrics to break.
There is a single dev environment where metrics work and currently no local way to determine if changes to our observability/APM code are working as expected. Deploying to the dev environment takes a long time, and it is possible that someone else already is using that dev environment. There needs to be a quicker, local way to verify observability/APM changes. Currently code can compile and tests can pass and our metrics could be completely broken.
The text was updated successfully, but these errors were encountered:
This is a task that was identified in the 10/13 retro:
I ended up
spendingwasting a lot of time trying to reproduce and determine why the metric-reporter Micronaut rewrite caused the metrics to break.There is a single dev environment where metrics work and currently no local way to determine if changes to our observability/APM code are working as expected. Deploying to the dev environment takes a long time, and it is possible that someone else already is using that dev environment. There needs to be a quicker, local way to verify observability/APM changes. Currently code can compile and tests can pass and our metrics could be completely broken.
The text was updated successfully, but these errors were encountered: