[MAGNOLIA-8093] Provide managed MeterRegistry from Magnolia Core Created: 12/May/21 Updated: 30/Nov/21 Resolved: 27/May/21 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
[X]*
MeterRegistry, e.g. start with one registry for all metrics
[X]*
New metrics can be implemented in a generic way (e.g. for DB, cache)
[X]*
Check out OpenTelemetry metrics (beta) for curiosity and future plans, but Micrometer should be good to go for now.
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Epic Link: | Metrics Scraping | ||||||||
| Sprint: | Cloud Service 9 | ||||||||
| Story Points: | 5 | ||||||||
| Description |
|
Provide a managed Micrometer MeterRegistry implementation from Magnolia Core at runtime, so that modules exporting metrics don't have to.
Implementation notesSee also description and ACs contributed by agarcia and mgeljic on CLOUD-161 (kept only a subset here), as well as parent Epic & Initiative for the end-to-end story.
Exact metrics we want to collect for Magnolia side will be subject of follow-up stories/tasks, e.g. success/error responses, request processing time, definition problems. |