Skip to content

Improve discovery of DataVerticle metrics #253

@s4heid

Description

@s4heid

Is there an existing issue for this?

  • I have searched the existing issues

The Problem

There is 4 different data verticle metrics that can be enabled. These metrics will be collected for every single DataVerticle if the feature is enabled.

This may be fine for small installations, but running NeonBee with a large number of DataVerticles will produce a huge amount of metrics and clutter the monitoring system.

Desired Solution

Two ideas to improve the discovery of the metrics:

  • instead of making the verticle name part of the metric name, a micrometer tag could be used. this would reduce the number of metrics to 4, but you would still be able to filter for a specific verticle (e.g. when creating a chart).
  • add a neonbee. prefix to each metric. The monitoring system might contain quite a lot of metrics from different sources with overlapping names. The prefix would make it easier to search for the neonbee metrics, if you don't recall the exact name. This should be a convention for all metrics sent by neonbee.

Alternative Solutions

No response

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions