[OAK-5973] Metrics integration should expose endpoints in an non flat name space

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: core
• Labels: monitoring production
• Assignee: Unassigned
• Reporter: Michael Dürig
• Created: 23/Mar/17 09:39
• Updated: 16/Nov/17 13:10

Description

The Metrics integration introduced with OAK-3654 exposes all endpoints in a flat namespace. This quickly becomes troublesome as I would expect the number of endpoints to quickly grow. We should come up with a way to expose them by grouping related ones together. Preferably in a similar way loggers are usually acquired and used to developers do not need to spend much time thinking about naming issues when introducing new endpoints. At the same time this would expose the endpoints in a way familiar from loggers.

Related discussion: https://lists.apache.org/thread.html/a331f826d0767c501864426b48255a82b9e92f5d8582e9cf107745cf@%3Coak-dev.jackrabbit.apache.org%3E

Issue Links

• blocks: OAK-5468 Ease TarMK Operations
• is depended upon by: OAK-5635 Revisit FileStoreStats mbean stats format
• relates to: SLING-6702 Make MetricsService accessible as easily as a Logger