thresholds

10 Topics

New Alert Threshold Options In Portal 200
We were reading through the new alert threshold options coming up and we are very excited. This will solve a ton of our problems and allow us to be more agile for our clients. Being able to control alert interval at various levels now and controlling no data is awesome! 1 issue tho. The continued bad design around UI v4.I use 4k monitors at 100%. Why in the world is the threshold adjustment so tiny and hard to work with? Now truthfully I don’t always go around maximizing my browser windows, but still. This feels like so much wasted space.
Joe_Williams
2 years ago Place Product Discussions
67Views
12likes
2Comments
Any way to only generate alerts during business hours?
Hi, We have a Datasource that runs a script to check the status of a Job. That Job only runs during business hours (e.g. 8-5 M-F). We need a way to not have it check after hours. Option 1 was to set a recurring SDT. This would stop the notifications, but the checks would still show as alerts in the UI so we don’t want that. Option 2 was to set Time-based thresholds within the Datasource. However, that doesn’t let you specify Days of the Week anywhere so that also won’t work. Anyone have any other ideas on how we can configure this to only check and alert during business hours? Thanks.
Kelemvor
2 years ago Place Product Discussions
109Views
9likes
4Comments
Ideas to maintain thresholds across thousands of devices and even more instances.
I have an ask to standardize some thresholds based on device type. We break out folders out like so: Clients/CLIENTID/Location/Techstack We then have roll up folders under each client for reporting/automation Clients/CLIENTID/ZZZ_Firewalls The ask brought to myself and my team is to standardize thresholds based on techstack. The first one I was given is that all Firewalls should have status and X% for in/out on Interfaces. My first idea was to script it and use our automation platform to run daily or every other day to check if a threshold is set, and if not, set it. The issue there is on the initial dry run, I am at over 11 hours and maybe 40% through. This script loops through each client ZZZ_Firewalls folder, gets the interfaces, then checks if a threshold is set. If not, it sets the base threshold. I figured I would break it in half A-N and M-Z and run both concurrently. But in testing M-Z, 1 client is taking almost 10 hours, and I have another of the same size in that block. I also have 1-3 clients of similar size in A-N. Second idea was to create a dynamic group that encompasses all of the /Firewalls/ devices and set the threshold on that folder. But I was leery of that as we could end up with oddities on deepest folder wins. We also cannot simply edit the datasource as this datasource applies to much more than just Firewalls. Any ideas would be appreciated.
Solved
Joe_Williams
2 years ago Place Product Discussions
155Views
7likes
6Comments
Can I set a different threshold for C drive from D or E drive space?
Hi, Our Windows servers have the standard alerting based on Volume Capacity. When Used Percent gets to 90%, we get a warning, 95% error, etc. How could we change this so that the C drive uses a different set of thresholds than the D drive? Can we do that within the basic DataSource or would we have to have one DataSource that just checks C and one that just checks D? I don’t want to clutter everything up, but if this is easy to do, it would come in handy. Thanks.
Kelemvor
2 years ago Place Product Discussions
193Views
6likes
5Comments
6 polls, 5 poll cycles, or 12 minutes
Alright, take a look at this. The poll rate for this DS is 2 minutes. What is the trigger window? Assume all the criteria is met starting a 1:59 PM and 30 seconds (between polls). When will the alert be triggered? It’s actually 10 minutes (2:10 PM, +/- a couple seconds for collector task queue delay and assuming original scheduling at the top of the hour). Do you know why? Why does it say 12 minutes? Why not 10? Is this behavior different than regular alert trigger intervals?
Solved
Anonymous
3 years ago Place Product Discussions
86Views
2likes
3Comments
Changes to the Big Number widget (more flexibility, this is a dashboard!)
A recent change to the Big Number widget has decreased formatting flexibility . It used to be that you could set thresholds to change colors if the number is between certain values and your "All other times" (else) condition could be any color you wanted to match the style of your dashboard. This allowed the flexibility to integrate the Big Number into your existing creative style with the added benefit of "POP" it falls below or between a certain lower threshold. For example, a red or orange number if server uptime is <=5 days, but grey or white text when that condition isn't met. After this recent change, anytime threshold isn't met the number is forced to be a "mild green" color which does NOT integrate well with most of the available Widget Appearance color schemas. Yes you can turn off thresholds and choose any number color you want, but you lose valuable attention-drawing functionality (which I would say is the point of this widget). In general, this really fouls up the asthetics of my client-facing dashboards. Have a look for yourself (attached). Please restore the flexibility (that we had previously) to change the Big Number "All other times" condition to something other than green. I'd suggest using the same color palat you get with the "Text" widget. This allows more visually flexible dashboarding and lets face it, dashboards are meant to be asthetically pleasing. Versatility of color goes a long way in achieving this. I've got a ticket open (99920) related to this suggestion, I encourage others to post comments (agree/disagree) here. Thanks everyone!
DBA_Troy
8 years ago Place Archive
8Views
1like
1Comment