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

Brick status value for "Gluster-at-a-glance" #365

Open
r0h4n opened this issue Mar 6, 2018 · 3 comments
Open

Brick status value for "Gluster-at-a-glance" #365

r0h4n opened this issue Mar 6, 2018 · 3 comments
Assignees

Comments

@r0h4n
Copy link
Contributor

r0h4n commented Mar 6, 2018

Attached screen shot, "Volume status" "Host status" show "status" column as 0 for active

But the Brick status has "status" column as 1 for active.

Any reason for this different behavior with brick statuses ?

screenshot from 2018-03-07 01-16-06

@cloudbehl
Copy link
Member

@r0h4n There is logic written in grafana for coloring the panel based upon these values that's why the different values are assigned to a different status.

volume status and node status comes as "UP" and "Down" whereas the brick status comes as "Started" and "Stopped".

Status Mapper[1] for grafana:

[1]. https://github.com/Tendrl/monitoring-integration/blob/master/tendrl/monitoring_integration/graphite/__init__.py#L566

@r0h4n
Copy link
Contributor Author

r0h4n commented Mar 16, 2018

There is scope to unify these statuses (up, started, down, stopped). @nthomas-redhat thoughts?

@shtripat @GowthamShanmugam

@nthomas-redhat
Copy link
Contributor

@cloudbehl , I agree with @r0h4n . This should be on the similar lines, otherwise its going to be really confusing. We need to take it up for this release.

cloudbehl added a commit to cloudbehl/monitoring-integration that referenced this issue Apr 4, 2018
cloudbehl added a commit to cloudbehl/monitoring-integration that referenced this issue Apr 4, 2018
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

No branches or pull requests

3 participants