13 replies to this topic

[tkrn]

I am having an issue and was wondering if there is away around it. Do I need to have a critical threshold? I am looking to only warn but not make the system as down. Is this possible?

Thanks!

[Chris Kasza]

You are not required to enter a Critical value; entering only a Warning value is sufficient.

Also, you only need to enter file systems in the Special Cases section if you have some file systems that you want to alert at a different capacity. Since you set the Global Warning Threshold to 85%, you don't need to have an explicit entry for /opt/asp/cachesys/mgr/journal at 85% as well.

[Chris Kasza]

What is the issue you are experiencing though?

[tkrn]

We've recently upgraded from Uptime 5 to Uptime 6. This is when this changed. I am unable to put nothing for a critical value. That journal file system it can (and does often) reach 100% but that doesn't mean it's down. There is an alternate 'rollover' location for the application which has much more storage. What is happening since I am forced to put a value, when it reaches 100% it marks the system as down which affects our SLA's which is not accurate.

In Uptime 5, you are correct you could leave the values out. In Uptime 6, you are forced to put a critical value in. Can I use the old script or can I re-import the disk usage script from Uptime 5?

Thanks,

[Chris Kasza]

I expect this was an intentional decision by Dev but I'll pass along a request to allow an empty CRIT threshold.

As a workaround, I suggest entering a very large number in the CRIT threshold field and select terabytes from the dropdown, so that the threshold is never exceeded (ex. 1000 TB).

[tkrn]

Great suggestion on the threshold for the critical values. I thought it was probably intentional by the development staff.

Thanks Chris!

[lefrajea]

I red all the post and I have a question I'm running version 5.5 and I have to enter a value for warning and critical. Is there a walk around to solve this situation. Thanks ins advance

[Chris Kasza]

lefrajea,

In up.time 5, you are not restricted to entering a value in the Warning and Critical fields; just make sure that nothing is selected in the dropdown and then you can leave the Warn or Crit field empty.

- Chris

[lefrajea]

lefrajea,

In up.time 5, you are not restricted to entering a value in the Warning and Critical fields; just make sure that nothing is selected in the dropdown and then you can leave the Warn or Crit field empty.

- Chris

Sorry but not sure which drop box your talking this is what I have only threshold % that it nothing else

Global Settings Retained Data Tracking
Global Warning Threshold %
Global Critical Threshold %
Exclusions

[Chris Kasza]

Sorry lefrajea; I mistakenly thought you could leave the field blank in up.time 5 but I guess I was wrong. I would suggest upgrading to up.time 6 to utilize the workaround that I suggested for tkrn. Otherwise, you could enter any values in the Global Warn and Crit fields and then add a Special Case entry where you can leave Warn or Crit empty.

- Chris

[tkrn]

Yes, Chris' workaround worked like a charm. Thanks again.

[lefrajea]

Sorry lefrajea; I mistakenly thought you could leave the field blank in up.time 5 but I guess I was wrong. I would suggest upgrading to up.time 6 to utilize the workaround that I suggested for tkrn. Otherwise, you could enter any values in the Global Warn and Crit fields and then add a Special Case entry where you can leave Warn or Crit empty.

- Chris

I'm now at version 7 but I'm still unable to leave the field Global Critical Threshold any idea why

[lefrajea]

I am having an issue and was wondering if there is away around it. Do I need to have a critical threshold? I am looking to only warn but not make the system as down. Is this possible?

Thanks!

Sorry I forgot a word so I'm unable to leave the field Global Critical Threshold empty is it normal from what you said I should be able to leave this field empty.

[Chris Kasza]

Hi lafrajea,

The product team has decided to stick with the current functionality of the File System Capacity monitor for the time being. The work around stated earlier, using a larger size than the actual disk capacity, is still the best way to eliminate CRIT or WARN alerts.

Regards,
Chris