Skip to content
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

feat(fluent-bit): Updated dashboard scope #391

Merged
merged 1 commit into from
Jun 23, 2023

Conversation

stevehipwell
Copy link
Collaborator

This PR fixes the Fluent Bit chart Grafana dashboard scope to work when there are multiple pods with similar names. It also updates Grafana dashboard components and schemas.

@stevehipwell
Copy link
Collaborator Author

CC @patrick-stephens

Copy link
Contributor

@patrick-stephens patrick-stephens left a comment

Choose a reason for hiding this comment

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

Not going to review the massive JSON but assume it is fine - any chance you can highlight the changes with a screenshot or something? Previously I did some CI around that - deploying it, running up Grafana then auto-screenshotting and adding to the PR but it is likely overkill.

I notice we increment the plugin version too.

Signed-off-by: Steve Hipwell <steve.hipwell@gmail.com>
@stevehipwell
Copy link
Collaborator Author

@patrick-stephens the dashboard should look pretty much identical. I used Grafana to update the dashboard components and then I scoped the queries to only select metrics from components owned by the chart.

I've also just updated the PR to make sure that the Prometheus job has a consistent name.

@stevehipwell
Copy link
Collaborator Author

image

@patrick-stephens patrick-stephens merged commit 9571226 into fluent:main Jun 23, 2023
2 checks passed
@stevehipwell stevehipwell deleted the fluent-bit-dashboard branch June 23, 2023 15:38
Matiasmct pushed a commit to giffgaff/fluent-helm that referenced this pull request Oct 24, 2023
Signed-off-by: Steve Hipwell <steve.hipwell@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants