• Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

89 Excellent


About mnagel

  • Rank
    Community All Star
  • Birthday July 17

Recent Profile Visitors

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

  1. mnagel

    SNMP Multi credential setter

    @Mike Suding Wanted to try this, but I guess it is very complicated -- still pending :(.
  2. We find at times the need to monitor usage on one device interface but show traffic information from another source. For example, we may get a utilization alarm from the physical crossconnect on an external switch to the ISP, but we have no useful traffic data (or no data) on that switch. The next step would be to go to traffic details on downstream devices, like firewalls. It would be helpful to have a "Related To" URL list available to avoid manual navigation each time. Ideally, this would be in the UI and available in alert tokens.
  3. In this case, yes. I never noticed myself, but can see why someone might take the instructions literally. I just hate too-strict systems that error out like this and frustrate users unnecessarily. We also link LM to ticketing in some cases, but found when it is done via email integration (easier with the ticketing system we use), LM made the decision that ACK and SDT notices are not sent via custom email integration, no way to fix short of development changes. Really need at least some folks over there focusing on the basics -- some of the new advanced stuff is nice, but poor alert handling (not this one specifically, which is annoying but at least can be worked around) is a shame.
  4. The current command-by-mail (when allowed, which is ONLY with the builtin mail transport) is a bit misleading especially to those not already familiar with LM. You may reply to this alert with these commands: - ACK (comment) - acknowledge alert - NEXT - escalate to next contact - SDT X - schedule downtime for this alert on this host for X hours. - SDT datasource X - SDT for all instances of the datasource on this host for X hours - SDT host X - SDT for entire host for X hours I had a customer literally put in: - ACK still working with century link because, well, that is what it says to do. Please fix so it is more clear, or fix the response handler to account for this use case. As always, the computer should be doing the work here, not offloading to busy humans.
  5. Sadly, no feedback at all on this from LM and it is a huge issue -- this is something we cannot workaround on our own, the tokens for step descriptions and other related details must be added to avoid sending useless information to our clients.
  6. Right now, we get only Resource counts from the LogicMonitor_Collector_GlobalStats datasource. We need to be able to show our clients their usage on ALL chargeable elements, including Website checks, LMCloud, LMConfig, etc. I have cobbled together something via the API to try to track this offline, but we need to clearly show clients what they have via a dashboard widget and right now the only one we can show is Devices (Resources). At the same time, please setup a way to define inputs to that via standard properties that indicates a client's subscription level, is possible. We hack around this now with a datasource that pulls in a property defined at their top-level folder.
  7. I am definitely going to check that out, Mike -- always wished we could have that in LM! To answer the original question, there is a way to detect SNMP access failures, but it relies on you knowing something that is not well documented. If you check the Uptime datapoint, you will find it has no threshold, but will generate a warning on "No Data", so: We always have rules like the above for each of our clients as well as similar rules for WMI failure. I have recommended previously that datapoints with "No Data" alerts are indicated in the tuning page along with regular thresholds.
  8. Yes, it is much better now, but still room for improvement (isn't that always true?). Dynamic tables do not support text variable display -- this would be super helpful to create lists of inventory items, device versions, etc. Instead you have to use the report function, which just makes it less accessible for casual review. Other products like SolarWinds can report changes in variables like firmware version, for which there is no option in LM short of the premium LMConfig feature, and that doesn't actually report changes unless you use an custom API script.
  9. mnagel

    !!! Collector Debug Console Security !!!

    Oh it gets better :). We had an issue awhile back (still do) that could only be resolved via an internal debug command (update system.ips property) normally run in the collector debug context. This is entirely doable via the API. No MFA required, no IP restriction possible. Chew on that one for a bit...
  10. mnagel

    Conditional EventSources

    I agree and raise you -- there should be a general correlation facility. I would be excessively happy right now to even be able to reference the value of a different datapoint in the same datasource in an alert string. The right solution would be to define correlation rules similar to Zabbix ( where you would suppress alerts depending on a complex evaluation of any LogicModule result. For events specifically, they themselves need to be bucketed with a "correlation key" and counters with alerts tied to more than just an ephemeral point in time (see SEC for a great simple-ish tool that does this for event streams (
  11. mnagel

    SDT "groups"

    Any thoughts on this? I really hate telling clients stuff like... "ok, here's what you do -- first navigate to resources and add SDT for all your hosts at the site. now, also go to the firewall external check and maybe website external checks and add SDT there. and also go the internal cross-site ping checks and add SDT there. oh yeah and you also need to add SDT to the collector" and such. Very clunky and error-prone. I should be able to setup an SDT group spanning all monitoring types representing a logical unit (like a site) and tell then to just set SDT for that logical unit. Again, constantly having to perform manual tasks like this creates pain and opportunities for error -- please make the computer do the job it excels at for us.
  12. mnagel

    resource timezones

    When will the resource timezones be implemented? Per-user timezones definitely helped, but then development just seems to have stopped. There are many reasons this is needed, for example, if an alert threshold or an alert rule has a time range, it should apply to the timezone of the resource (or at least be able to). Chart display relative to the resource timezones is another use case.
  13. mnagel

    Dashboard Templates

    This same problem exists in much of LM -- encouraging cloning with lack of an inheritance feature is the root cause. I agree this is needed as it is needed for LogicModules and pretty much anything in the system.
  14. The real problem with all of this is lack of full template support (with conditionals and other logic structures found in Jinja2 for Python or any of the various Groovy engines (e.g., Since everything is static with value substitution, you get stuck very fast trying to generate useful results. The per-datapoint alert template is a decent workaround for datasources, but there is nothing similar for any other logicmodule, unfortunately. We solved a lot of it by sending all the tokens via an email integration where they are unwrapped and processed before generating a ticket with the result, but you need tokens to make it work. And we get stuck due to some odd design decisions (e.g., acks are not sent via the custom email integration...because). I once was asked to include a documentation note for a client in their alerts (only theirs), but there is no way to do this short of editing every template, including datapoint templates. This is what support told me to do -- for real. You can't use a custom email integration because you lose the ability to respond to ACK/SDT and you don't get certain messages, like ACKs.
  15. If a step fails in a website check, the step description should be produced in the alert. I am very tired of fighting with the system to get it to do the correct/obvious thing and my clients find it ridiculous to have to dig around to know what is actually happening. Please make the computer do the work so we don't have to.