Steve Francis

LogicMonitor Staff
  • Posts

    267
  • Joined

  • Last visited

Everything posted by Steve Francis

  1. You can import the UCS datasources, which give you hardware monitoring among other things, from the core repository. From Settings...Datasources...Add From LogicMonitor Repository. Sort by name, and check all the Cisco UCS ones to import.
  2. It seems unusual for an SNMP query to return a JSON object (can't recall ever coming across such a thing), so at the moment, I don't think we'd put this on the roadmap. That being said, you can do this with a little more complexity. You can create a complex datapoint that puts all the power of groovy at your disposal to do whatever you want: http://www.logicmonitor.com/support/datasources/creating-managing-datasources/complex-datapoints/#Groovy-Script You'd add a regular datapoint that collects the data as an OID. (Doesn't really matter how it's defined.) Then a complex datapoint, that can access all the raw data returned by all OIDs, by using a map. So adding two datapoints: datapoint1 = .1.3.6.1.12.12.12 datapoint2 = .1.3.6.1.12.12.13 You can access them in groovy as: d1= output[".1.3.6.1.12.12.12"] d2= output[".1.3.6.1.12.12.13"] The d1 and d2 will contain the raw output of the SNMP response, and can be processed in groovy/java as you like...
  3. And is now available under Setting.. Account..Financial.
  4. Filtering, progress indicators, deduplication - now all in the updated netscan! (so long as you use 21.020 collector or later.)
  5. Hopefully you've noticed from release notes or your account manager - but the NOC widget has fully supported glob matching for a while now. Sorry we didn't update here...
  6. Confirmation prompt is there now. Recycle bin is oft discussed, but still hard....
  7. Dead hosts now have the skull and crossbones icon next to them to indicate ... deadness.
  8. Yes, yes and yes! Sample dashboards are coming very soon (example cool dashboards for VMware, Linux servers, Windows and collectors, at least initially.) A specific datasource community is being built right now. Being able to exchange dashboards is interesting. Right now, you could start a thread in Ask the Community. If it's popular, we could promote it to a specific top level topic...
  9. The current UI has such links for all resources, so you should be good to go!
  10. You can now set up Audit Log reports that regularly run and send a complete or filtered set of the audit logs to a report that is delivered automatically. http://www.logicmonitor.com/release-notes/v76/ I'm not sure about the "alert on specific kind of Audit log entry" idea. How would you distinguish between something that was done correctly, and something that wasn't, if every type of action of a certain class triggered an alert?
  11. Ping checks in Services had response time alerts added at the start of the year. Hopefully everyone noticed from the release notes or their account managers! (We'll do better at responding to these requests, too.)
  12. Services API has been out for a while. Sorry we didn't notify! http://www.logicmonitor.com/support/rest-api-developers-guide/services/
  13. We added this functionality a while ago. Hopefully you picked that up from the release notes or your account manager!
  14. Hopefully you noticed that became available in January this year... The ##POLLINTERVAL## token. http://www.logicmonitor.com/support/datasources/creating-managing-datasources/tokens-available-in-datasource-alert-messages/
  15. Hopefully you're aware of the Big Number widget, that's been out for quite a while, that allows exactly this!
  16. Hi Kris - came across this old post when I was looking for somethign else.. THis shouldn't happen. The flap alert only triggers when the interface is up (but only recently up). When you unplug an interface, status will go down, which should remove any status flap alerts, as they are conditional on an UP state. If this is still occurring, LMK and I'll investigate in your account. Thanks
  17. There's a fine line between sending too many alerts and not enough. When an alert increases in severity over the state it was acknowledged in, we treat the new level as un-acknowledged. But in this case, the alert has been acknowledged at the critical level. If it drops to error, but doesn't clear entirely, then goes back to critical, we regard it as being in the same alert session -so the same critical acknowledgement applies. If the alert entirely clears, the future increases to critical are not treated as acknowledged. We do this for a few use cases: a metric that is oscillating over a threshold. (e.g. a disk volume that is 97%, then 98%, then 97%, then 98%, then 97%, etc) You probably do not want to have fresh escalations each time it bursts over 98%. philosophically, the system is treating the acknowledgement of the alert at the critical level as someone saying "I will assume ownership of this issue, up to this severity." In this case, its the maximum severity (critical), so it is ownership of the issue until it clears. If you want to prevent alert escalation of the criticals, but are unable to clear the issue, I'd suggest not acknowledging the alert immediately - instead put the instance in scheduled downtime for 1 hour (which will stop escalation). Work on the issue, clear it to error (or warn). If you are unable to improve beyond that, acknowledge that state. (Or adjust thresholds.) Then a future increase to critical will be escalated.
  18. In order to simplify things (for users and for our developers), we are debating whether we can drop support of 32 bit collectors, so all new collectors will be 64 bit. Very few people ever download the 32 bit collectors, and the ones we have reached out to have said they could run 64 bit. Anyone got a compelling case for still running a 32 bit collector?
  19. So the only requirement for this is to have some way to know what the interfaces 'real' speed is. If you can get the Bandwidth description via SNMP (which I could not find an OID for), then it's easy. Add a datapoint (say, 'RealSpeed') that gets that speed via the right OID to the Interfaces datasource. Then change the Utilization datapoint expression from this: InOctets*8/if(lt(BasicSpeed,4294967295),BasicSpeed/1000000,Speed)/1000000*100 (which says divide inOctets *8 by BasicSpeed, if BasicSpeed is less than 4294967295, else by Speed) to InOctets*8/if(un(RealSpeed),if(lt(BasicSpeed,4294967295),BasicSpeed/1000000,Speed)/1000000*100,RealSpeed) (which says divide InOctets * 8 by RealSpeed, unless RealSpeed is unknown - else use the original expression.) This assumes that the OID reports nothing if that bandwidth description is not set. If there is no OID to get the 'real' bandwidth, you will be able to manually set a property on the instance level where you can define the real bandwidth, and then you could use the property in the expression. Instance level properties are being developed right now, so should be released within 3 months.
  20. And hopefully everyone noticed the PagerDuty (and Slack, and other integrations) got a heavy revamp recently: http://www.logicmonitor.com/release-notes/v-71-new-device-tree-table-widget-slack-and-pagerduty-integrations/
  21. The current UI does exactly this. :-)
  22. You can now search on the notes field in the current (not the old) UI.
  23. Hopefully you've noticed this is something you can do in the current UI.