![]() |
![]() |
Subject: | Unable to get filesytem thresholds to work |
Author: | [Not Specified] |
Posted: | 2014-12-31 09:31 |
Subject: | http://www.zenoss.org/forum |
Author: | Jan Garaj |
Posted: | 2014-12-31 12:01 |
http://www.zenoss.org/forum/2551
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
Subject: | Thanks jan, I was able to |
Author: | [Not Specified] |
Posted: | 2015-01-02 08:09 |
Thanks jan, I was able to create a local copy and edit the thresholds however the thresholds seem not to be effective. I.e i made the max threshold value 30% by setting the max to here.totalBlocks * here.blockSize / 1024 / 1024 * .3 , on my system i had 3 disks out of 4 that were using more than 30% disk space but the the thresholds do not seem to be generating the warning for over 30% usage
Subject: | One image will be better than |
Author: | Jan Garaj |
Posted: | 2015-01-02 10:21 |
One image will be better than one million of words. Here is: http://i.imgur.com/HexGjyG.png
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
Subject: | thank you |
Author: | [Not Specified] |
Posted: | 2015-01-02 17:01 |
thank you
< |
Previous Url not found |
Next While adding a New Device - A Zenoss error has occurred : An error was encounte ... |
> |