pmeyer

Members
  • Content Count

    21
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by pmeyer

  1. What is the value that 'onetimeUpgradeInfo' should be set to?  I tried setting it to '27003' (as an integer), and the call comes back as 'Invalid json body'.

    {
        "collectorGroupName":  null,
        "description":  "lsfregprd-Collector for vpc-0e4ddd0f271668f34",
        "onetimeUpgradeInfo":  27003,
        "enableFailBack":  true,
        "suppressAlertClear":  false,
        "escalatingChainId":  3,
        "backupAgentId":  0,
        "enableFailOverOnCollectorDevice":  false,
        "collectorGroupId":  null,
        "resendIval":  0
    }

     

  2. I would like the REST API to support

    • Scheduling a collector version update
    • Applying a one-time collector version update
    • Working with the Collector Custom Properties (recently added I think, but don't see anything in the online documentation about support in REST API).
  3. Is there a way (other than dredging through each device datasource via the API) to get a report on all the Alert Overrides that have been set on devices and device groups? Could that be extracted from the Audit Log w/o a lot of noise with it?

  4. On 1/27/2017 at 2:37 PM, mnagel said:

    That solution fails for SSL certificate expiration days remaining, unless you like seeing negative days.  We found a workaround by using a max of 90 days to see only those expiring in that period, but bottom 10 (or N) would be very nice to have as a general tool.

    Mark

    We're also running into the SSL cert expiring issue & would be beneficial to have a "Bottom 10" so we can see which ones are the more urgent to resolve.

  5. We are having issues with people disabling alerting on a device or device group but not adding a reason why it's being done.  It is difficult to find these things in the audit log as well.

    I would like to be able to make adding an Ops Note a requirement when turning off (or on) Alerting.  Now that the graphs add the tag, and if it's enforced, it would be then easy to see why metrics went away (and then came back).

    • Upvote 1
  6. When building a report, I would like to be able to exclude things. There are scenarios for excluding...

    • Exclude groups - We have a lot of device groups.  It would be simpler to be able to exclude 1 or 2 groups instead of adding 2 dozen or more groups.
    • Exclude devices that are in an SDT
    • Exclude devices that have Alerting/Monitoring disabled - People are running reports and then asking me why some have "No Data"... that's usually because alerting has been disabled, but it's still in the report because the device matched the criteria.  This is causing a lot of "run-around" to cross-reference the reason and give feedback.  And then it happens the next day because people forget why.
  7. I also have scenarios where I would like to schedule a datasource to only run at a certain time of the day - maybe like Windows Task Scheduler. 

    Example - Pulling disk defgrag reports overnight.  With large volumes, this may take a while to execute.  I'd really only want to execute it overnight - or maybe even once a week.

    I know I can set the ".pollinginterval", but I can't make it execute at a certain time. It's still a bit arbitrary on when it does the 1st check, which then determines the time for all future checks.

  8. I would like the ability to "Lock" a Datasource, so that it's harder to be accidentally changed.  Had an issue today where I changed the wrong Datasource - they were named very similarly.  Having to go through one more process to "unlock" would be useful.


    Or - have a way to "version" a Datasource & be able to 'roll back' to a specific version if necessary.

  9. When AWS Devices are returned by search, almost all of the device names are cut off.  This makes it difficult to find the device since the most relevant piece cannot be seen.  Would like to see the search be enhanced with one or more of the following:

    • Auto-expand the results like it does today when looking @ metrics with long names.
    • The ability to have a floating search pane.
    • The ability to have the full name show when hovering over the device with the mouse cursor.
  10. Having a Bottom 10 would help with finding devices that don't stay up for very long.  Or, in my case, trying to find the collectors that are restarting the most before the 8 hour window.  For now, I did make a Virtual datapoint to subtract the Collector Uptime from 480 for the top 10, but then people reading it would really need to "know" that collectors are restarted every 8 hours.

    Being able to just show the Bottom 10 that have the smallest Uptime would be easier to understand by the ones that will be looking at the graphs.

  11. Today we were flooded with hundreds of alerts in our alert dashboard.  AWS was having an issue in the ap-southeast-1 region with launching new instances.  The "AWS Service Health" datasource found this issue and then alerted on it for each instance & ebs volume we had in that region.

    That was too many alerts, especially since the issue wasn't with our existing devices in that region.

    I would like this alert to happen on the AWS Device Group itself - per region, so that we can know about it, but it won't generate an excessive number of alerts with the same exact information.

  12. I want to be able to search on the Device Group Description by using "gd:". Similar to being able to use "g:" to search on group. Other types of searching would be helpful as well, like on custom properties.. "cpn: & cpv:" for Custom Property Name & Custom Property Value, similar to filtering in the REST API. 

    • Upvote 1