Sarah_Terry
Product ManagerJoined 10 years ago
User Profile
Product Manager
User Widgets
Contributions
Re: Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from legacy UI
Hi Kelemvor - I would love to set up some time to talk through your specific feedback & what complaints you have. While I agree the new UI transition has been painful, we have worked very hard to resolve bugs & performance issues, and you should not still be seeing these issues. Many complaints about the new UI came from an earlier period in the transition, and have long since been addressed. In addition, the new UI includes many new features you won't find in the older UI (like dashboard filtering, resource explorer, datapoint analysis, logs analysis, netflow sankey, DataSource level alert tuning, and more), so sticking to the older UI means you are not getting the best of LogicMonitor. Lastly, we are only have plans to force the following three pages, currently: Settings, Reports, Websites -- and thats because these pages are simpler, the adoption is high, and issues very few and far between. We know Dashboards & Resources are more complicated pages and we want you to feel comfortable before we remove the toggle -- again would love to chat about what you're seeing & what would make you feel comfortable with the new UI.14Views2likes0CommentsRe: LogicMonitor "Application ELB" Datasource returns NoData instead of metric for ELB 5XX
Yes - it is because CloudWatch doesn’t actually report 0s via the API. So that means No Data could mean: there is no data because the load balancer is unresponsive or otherwise not working, OR it could mean: the value is 0. One reason we don’t automatically change No Data to 0 is that it eliminates the ability to alert on that first No Data condition (the load balancer will always appear to be working from a monitoring perspective if we default No Data to 0). The best option is to use the complex datapoint option above, but instead of doing it based on the raw metric, use a different datapoint that should always return a value when the resource is functioning (like HealthyHostCount). We are trying to add these complex datapoints to more of our cloud out of the box modules.14Views4likes0CommentsRe: Is it feasible to get data for EBS from CloudWatch metrics at every minute interval?
EBS CloudWatch metrics are available at 1 minute intervals (see https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/using_cloudwatch_ebs.html), so you can just change the polling interval in LM to 1 minute. The reason we default to 5 mins is to optimize CloudWatch costs out of the box -- the 1 minute polling will get you more granular data (and alerts), but it will add more to your CloudWatch bill as well.32Views2likes0CommentsRe: Details for the CloudWatchProbe feature?
Hey @Brandon- That note is intended to capture a change for our cloud collector in which we've improved how we're making the CloudWatch getMetricStatistics requests to be more efficient, but the details here (v3, CloudWatchProbe) are more specific to our internal teams. Sorry for the confusion - we'll clarify the release notes.11Views1like0CommentsRe: Aruba Central monitoring
Hi @SeanStarson - We're looking into this, but don't yet have any official plans. We'll keep you updated with progress :)/emoticons/smile@2x.png 2x" title=":)" width="20" /> Thanks @Michael Dieterfor the detailed response on desired monitoring! Ideally we'll build this as a cloud integration since the information is available via API, but traditional DataSources may be a faster short term option.83Views0likes0CommentsRe: 22 July 2020 - Dynamic Thresholds
18 hours ago, David Good said: Also, what happens if you have, say, a dynamic threshold set for disk usage and the usage grows very slowly and steadily. If I also have a static threshold set for when the disk is dangerously full will it still send notifications or will they be suppressed since the value isn't anomalous? It's possible if the usage is slowly & steadily increasing that the band will adjust to that usage. You can avoid suppression by having static & dynamic thresholds at separate severities (eg static threshold for critical severity & dynamic for warn | error). Sometimes these metrics where you generally know that certain good and bad ranges always hold true (e.g. above 90% is always bad, below 90% is always good) are a better fit for static thresholds. Dynamic Thresholds are most useful when it is not possible or difficult to identify a range generally/globally across all instances (e.g. above 10MB/s may be bad for instance A, but for instance B it should be above 100MB/s).3Views0likes0Comments