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 Dashboard for settings adjustments #22

Open
survivant opened this issue Mar 23, 2021 · 3 comments
Open

Grafana Dashboard for settings adjustments #22

survivant opened this issue Mar 23, 2021 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@survivant
Copy link
Contributor

I'll look to have a dashboard that can help us to identify which drives can't handle the throughput or which ctor pool doesn't have enough resources to handle the "charge".

Let me explain in more details.

It's possible to configure the ctor pool with those settings

# values for the volumes
    volumes:
      queueDepth: 32
      luWorkers: 16
      zvolWorkers: 16
      resources:
        requests:
          memory: "64Mi"
          cpu: "250m"
        limits:
          memory: "128Mi"
          cpu: "500m"
      auxResources:
        requests:
          memory: "64Mi"
          cpu: "250m"
        limits:
          memory: "128Mi"
          cpu: "500m"

but it's possible that my settings are too low. It will be useful to see in a dashboard /alerts to AlertManager too, that I have a ctor pool that is overloaded. Not enough resources to handle all the requests. Like a gauge or Health bar.. RED when it's overloaded.

same thing when the pods are trying to write in a pool and the drives are not able to support it.. a RED health bar.. or a gauge : max throutpuyt supported / current. Something that will tell us that the drives are overloaded and we need to reduce the speed that we write on them.. or change the pool to include another disk ?..

At this point, I changed the settings without knowing if it's too much are not enough.

@survivant
Copy link
Contributor Author

@Ab-hishek is it something that can be done ?

@Ab-hishek
Copy link
Member

Will have to dig deep into this. Will do some initial research and then get back to you on this @survivant .

@kmova kmova transferred this issue from openebs/charts May 25, 2021
@avishnu
Copy link
Member

avishnu commented Sep 11, 2024

CStor has been deprecated starting OpenEBS v4.0. This issue could still be relevant for other projects having pools, eg. Mayastor. IMO, the requirement here will be to be able to identify and export adequate metrics that represent this 'state'.
Anyone willing to give this a shot, please comment here.

@avishnu avishnu added the help wanted Extra attention is needed label Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants