Skip to content

[ECOINT-212] Redpanda v2.1.0 - Support for lag metrics #2719

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 16 commits into
base: master
Choose a base branch
from

Conversation

pmw-rp
Copy link

@pmw-rp pmw-rp commented Jun 18, 2025

What does this PR do?

This adds support to the Redpanda integration for native lag metrics.

Motivation

New feature availability within Redpanda.

Review checklist

  • PR has a meaningful title or PR has the no-changelog label attached
  • Feature or bugfix has tests
  • Git history is clean
  • If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
  • If this PR includes a log pipeline, please add a description describing the remappers and processors.

Additional Notes

Anything else we should know when reviewing?

BenPope and others added 11 commits June 18, 2025 09:57
The tests now pass.

Signed-off-by: Ben Pope <[email protected]>
As of Redpanda v25.1, some consumer group metrics can be disabled
by changing cluster config "enable_consumer_group_metrics".

These are still enabled by default, but split them out into their
own grouping.

Signed-off-by: Ben Pope <[email protected]>
Signed-off-by: Paul Wilkinson <[email protected]>
@dd-dominic dd-dominic changed the title Redpanda v2.1.0 - Support for lag metrics [ECOINT-212] Redpanda v2.1.0 - Support for lag metrics Jun 18, 2025
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My recommendation is to add these 4 widgets to the current dashboard (using a separate grouping widget). Once merged, these changes will be reflected in the original dashboards for existing customer installations.

If you'd like to keep this second dashboard, that's fine too.

In either case, the dashboard(s) will need to be brought inline with our best practices. See attached dashboard template.
Integration_Dashboard_Template.json

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where can we find documentation on the dashboard best practices? Is this json template the only description of this?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hcoyote, I've found the best practice guides and have started reorganising the dashboards accordingly.

@dd-dominic, thanks for the recommendation, but I think we'd prefer to not have them in the main dashboard:

Firstly, there's a somewhat different audience for the lag metrics (Redpanda users interested in how their applications are behaving) vs the rest of the metrics (Redpanda administrators interested in how the cluster as a whole is behaving).

Secondly, the lag metrics are optional on the Redpanda side, and are only emitted once RP is configured to do so - so having them not show in the default dashboard feels off.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood, makes sense. Just make sure to update both dashboards to mirror our template as much as possible (colored group headings, branding/image, title casing, etc.)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. It would be lovely to be able to specify our own branding colours via a hex code though 👍

Copy link
Contributor

@sarah-witt sarah-witt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! I just had one comment about testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants