DBA_Troy

Members
  • Content Count

    8
  • Joined

  • Last visited

  • Days Won

    2

Community Reputation

4 Neutral

About DBA_Troy

  • Rank
    Community Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It looks like a recent patch has resolved this, thanks for listening Logic Monitor!
  2. 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!
  3. DBA_Troy

    Failover Collector confusion

    Perfect, thank you!
  4. The SDT feature is critical for a monitoring tool to be able to schedule blackout periods ahead of time. A lot of clients schedule their maintenance windows on a certain weekend of the month and your tool only allows you to set up repeat schedules daily at a certain time, weekly on a certain day, or monthly on a certain day of the month. This covers a lot of bases, but it's not how a good number of clients schedule regular downtime. For clients who schedule their downtime on the "4th Saturday of every month" you have to manually enter these dates as there is not way to automate it on a repeat basis. I suggest adding a "Nth weekday of the month" option so one can schedule based on the "1st Sunday" or "Last Saturday" or "4th Wednesday". This is common enough to be very useful. Thanks!
  5. I think it would be useful to have a widget that was a simple red/green light. Maybe red/green/off. Maybe one big light or a grid of lights with description (to save space), or both! This would be great for Windows (or other) services on dashboards. Any metric that is represented by a graph that is either a 1 or a 0 is pretty boring to look at. A simple green light = 1, red light = 0, lights out = NULL would be aesthetically pleasing. I'm a SQL DBA and having this for my SQL services would be a great way to jump on and see if anything is not running that should be (even if I don't necessarily want to be alerted that it is not running). Thanks!
  6. Dashboards are a fantastic feature, but the way the widgets and data source graphs snap is a huge inconvenience. Everything shifts up/down, nothing shifts left/right. If I make a grid of widgets that runs left-to-right (say each row is a server), it makes adding a new server to the bottom very simple. It (however) makes adding a new metric column a HUGE pain in the butt. If I want to add a new column to the left (for each server - like a new metric), I have to move EVERY.SINGLE.GRAPH in the whole dashboard to make it all line up... I think a FAR better approach would be to have the dashboard grid simulate the face of a smartphone. If I move a widget above another, it should shift down (like it does). If I move it to the left, it should shift right, not down! This would make designing an organized dashboard SO much easier (I've literally spent hours just adding a single metric across all our dashboards because of this stunting behavior). P.S. - also consider giving the ability to bucketize groups of graphs. Giving me a colored backdrop to put behind all my CPU metrics or all of my metrics regarding ServerX would be a nice visual aesthetic.
  7. LM Team, When you are on your primary collector and choose a failover collector and are deciding to check that box "Automatically failback when THIS collector becomes available again". The way that it is worded, THIS collector could mean the current collector you are configuring. Then again, the checkbox is underneath the failover collector you just selected and it is indented, so it's easy to convince yourself that it could be referring to the failover collector. I think it would be worth re-wording or at least offering a hover-hint (?) box to clarify that the failback will be occurring on the collector you are currently configuring. Looking back, I had checked this box differently depending on how I felt that day and which made most sense to me at the time. Some clairification would be good. Thanks!
  8. I think it would be really useful to have a button in every user profile that allows you to "re-send activation email" or "re-send registration email". This way if a user doesn't sign up right away and loses track of the email they got as a new user, you can easily go into their account and re-send that email to them rather than having to reset their password and crafting an email indicating this.