Simon Bingham

  • Posts

  • Joined

  • Last visited


0 Neutral

About Simon Bingham

  • Rank

Recent Profile Visitors

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

  1. We are still in need of this feature, I've just been explaining to a new starter who asked the question how we cannot pull arbitrary values such as software versions, ( easily )
  2. Thanks for the reply Steve, The devices we are looking at today are Junipers so the sysiod does not include the software rev, I was aware of the using the name for the datasource method but it is a bit as you say its a bit cludgy, it comes with a graph of no data, and I think ( but could be wrong ) that we have to display the serial number ( or other OID ) with the host, it leads to some interesting discussions with customers like why are you suddenly trying to graph a serial number ?. Ideally it would be great to have something more flexible and have the option for this not to be displayed.
  3. I know I've mentioned this before, one of engineers just visited me and asked "is there anyway LogicMonitor can give us the software revisions in use on all the devices on a customer network" I think the answer is still no. It seems we have a lot of the components in place, we know the the system OIDs for this data. we have an LM collector and all the customers 100s of routers added. But LM does not allow us to pull back and display arbitrary data from devices, with no interpretation. There is so much information we could potentially harvest from the products, Serial numbers, software version, product names and descriptions.
  4. I think we have requested this already but I just wanted to re-iterate this. 1) Currently the only arbitrary information from the MIBss that can be displayed with the host is the “sysinfo†field, there is pandoras box of more information we would like be able to display and include in the alerts this might include, Serial numbers, software versions, hardware types, hostname ( as the device sees its own hostname ). The request is to be able to read and display arbitrary information from the device MIBs in the monitoring. just to able to display the RAW text, no interpretation of the data whatsoever is needed. 2) A second and possibly different request is that all this info can be pulled from the system in the reports, as long as we can get a CSV file out with the raw data, that should be enough.
  5. Cloning rules in the rules set. Most of our customers are setup in an identical fashion. The time consuming and error prone copy and pasting bit by bit the elements needed to create a rule leaves me thinking, there must be a better way. If I could just hit a CLONE RULE button and instantly have a copy of a existing rule, all we would need to do is change the group-name and the escalation chain, job done.
  6. The same goes for escalation chains, we have some quite complex escalation chains and the ability to clone them would be a god send
  7. I'm aware of the downloading of the access log but we have a requirement for something more akin to to SYSLOG where we can quickly go back years if needs be and find out for for example why and who disabled alerting on a product. It's a difficult conversation with a customer when this cannot be explained.
  8. We increasingly have the need to be able to determine exactly who did what and when. For example if alert has been disabled for a host, it would be good if we had a record of who did this. The access log contains all the right information but does not go back far enough. Could we receive and email every time someone undertakes any activity pertaining to the configuration LogicMonitor (preferably), or otherwise could we get a monthly digest before the access logs are lost.
  9. 1) Can the engineer that clicks through and acknowledges an alert be added to the CC list for the duration of that alert. 2) If the engineer responds to the alert email by a reply, can their “from†email be added to the CC list for the duration of that alert
  10. Enhancement suggestion When we do the host --> Manage Alerts and Thresholds > Show Alert Routing > Test Alert Routing > Send Test Alert. This does fire off an email, but does not really represent the datapoint in question, the email is completely generic. For Example, we are customising the Alert Template for PingLossPercent, sending a test alert does not trigger this template, It would be better if the test alert looked exactly as if this data point triggered the alert, apart from ** THIS IS A TEST ** added in the subject line. As it stands I cannot really test if our new alert templates are working without triggering a real alerts. Which is a bit of a problem