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

Grafana doesn't show multiple cluster Pelorus metrics #1110

Open
1 task done
pacopeng opened this issue Nov 29, 2023 · 1 comment
Open
1 task done

Grafana doesn't show multiple cluster Pelorus metrics #1110

pacopeng opened this issue Nov 29, 2023 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@pacopeng
Copy link

OpenShift version

4.10

Problem description

Pelorus insance on 4.10.60 , Pelorus operator version 0.0.8

image

Pelorus instance on 4.12.29, Pelorus operator version 0.0.7

image

Since both Pelorus have shared S3 in the backend as the this link mentioned , metrics from both instance will be stored in S3. and the both grafana should display all of the datas.

Steps to reproduce

  1. install Pelous on OCP1 and configure S3
  2. install Pelous on OCP2 and configure with the same S3 bucket
  3. create deployment on both instance

Configure file
Archive.zip

Current behavior

each grafana can display it's own instance metrics and does not display the other's metrics stored in S3

Expected behavior

each grafana can display all the metrics from S3

Code of Conduct

  • I agree to follow Pelorus's Code of Conduct
@pacopeng pacopeng added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 29, 2023
@pacopeng
Copy link
Author

How long it takes to reflect all metrics in every grafana dashboard?

rolled out application on prod
image

rolled out application on dev
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

1 participant