Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-8093

Provide managed MeterRegistry from Magnolia Core

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Neutral
    • 6.3.0
    • None
    • None
    • None
    • Cloud Service 9
    • 5

    Description

      Provide a managed Micrometer MeterRegistry implementation from Magnolia Core at runtime, so that modules exporting metrics don't have to.

      • First implementation may be only a plain JmxMeterRegistry, with additional configuration coming up later (e.g. making it a composite, and/or configure for prometheus or datadog).
      • No need for the AOP-style instrumentation quite yet, will depend on use cases

      Implementation notes

      See 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.

      • 1 MeterRegistry per metric category or 1 MeterRegistry for the whole Magnolia runtime (in the end all metrics are scraped in one go)
      • or e.g. split business vs. performance vs. resource usage vs. uptime MeterRegistries to facilitate internal troubleshooting, avoiding one god object, etc.
      • Inject MeterRegistry vs. let registry discover meters/gauges/timers implementations
      • consider CompositeMeterRegistry, could be used by JMX collector and send to exporter

      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.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              mgeljic Mikaël Geljić
              mgeljic Mikaël Geljić
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoR