drewwats

Members
  • Content count

    10
  • Joined

  • Last visited

  • Days Won

    1

Community Reputation

2 Neutral

About drewwats

  • Rank
    Community Whiz Kid
  1. Great, looking forward to it!
  2. https://www.logicmonitor.com/support/dashboards-and-widgets/widgets/advanced-custom-graph-widget/ According to your page, this is normal behavior but, as shown in the image attached, the default use of instance name can be quite a hindrance to usability of the legend. I tried to define the Legend entry but that value gets pushed off to the far left by the defaulting instance value - which in most cases is useless and in this case is just a duplicate of the datasource name.
  3. In the case of JDBC collection, there are many times when a query runs long due to load on the DB and is killed by LM according to the configured timeout. This action is appropriate but the resulting "No Data" is mostly undesirable. In the "If there is no data for this datapoint" dropdown, I would like to see an option for "Use Previous Data". I know in many instances, "No Data" is a really bad thing but, in others, it is not. Instead of breaking all my dashboard widgets and seeing "NaN" in raw data, I would prefer seeing a limited amount of old data. 1-3 polling cycles would be a reasonable length of substitution before returning to "No Data" or "not a number" results.
  4. Just ran into this today, needed to add a %. I'm also not a fan of the default dash between unit label and bottom label. If I don't want to use a unit label, my bottom label always begins with a dash.
  5. What I'm picturing is a hybrid of the NOC widget and big number widget. The big number (text color or background color) would be in green when not triggering any alert conditions and yellow, orange, or red to match alert level. Alternatively, adding a value column to the NOC widget would accomplish the same goal. Either of these allows the eye to be drawn to the most important things on a dashboard without having to dig for the associated value.
  6. Agreed.
  7. I am familiar with this method but this doesn't easily accomplish what I'm talking about. And not every customer is proficient in scripting, I'm sure. The idea is to allow what already exists as independent datasources to be combined into a dependent metric without any redundancy of data collection. The uses for this are varied. CPU/memory/volume stats for nodes in a working cluster could be averaged into an overall cluster monitor. A datasource indicating a critical job is filling a message queue combined with an alert that a consumer service is not running could be of higher criticality than either of the 2 pieces of data alone.
  8. If I had one wish... Alert conditions being met could trigger execution of a script I know this may not be on the near-term radar, but this would be the feature that takes the product to the next level. Fortunately, most of the functionality is already in place; scripts can be ran on remote machines as a datasource. Adding the ability to run our own custom groovy (or whatever) scripts would allow error recovery actions and self-healing. Just guessing, but many customers may be willing to pay more for this. I just wanted to put this idea out in the forums and see what happens...
  9. Is there any possibility of creating complex datasources in the future? I would imagine it being similar to complex datapoints from the user perspective and could be even more useful.
  10. Is there any update on this?