jmontague

Comments

  • Marc! you had it right from the getgo! I used "insert variable" to add your original idea. I then just pasted it right into the message, and it works! And the corresponding email: Thanks for your help on this!!
    in Network Discovery Alert Variables Comment by jmontague January 2017
  • The nightly scheduled scans did not report the correct line. They all say: I feel like there is something simple missing in the SQL. I'm not sure how to test what it might be.
    in Network Discovery Alert Variables Comment by jmontague January 2017
  • SO SO very close!! i really appreciate the time thus far! Here is what i added to my alert: And here is the email from a discovery job called "Manual_Scan": It got the right variable (or it just grabbed the first entry in the table ). I left it in the email and i'll check the emails i get overnight from the scheduled…
    in Network Discovery Alert Variables Comment by jmontague January 2017
  • So the only other work around I can think of is to use Policies/Rules to execute "remediation" scripts. It doesn't fix your need for tier 1 support work type tasks, but it could save me from 500+ switch configurations..... Any thought on policies/rules? Same principal i suppose, check config for X - if present execute the…
    in Config Change Template for Syslog Comment by jmontague May 2017
  • Sorry it took so long to get back on this. I appreciate the effort! I'm running NPM version 12. First problem, i must have wrote the table name wrong in my question. Trying your script i realized the tables are: DiscoveryLogs DiscoveryProfiles Not sure where i got DiscoveryJobs at (maybe it changed in a version??) I can't…
    in Network Discovery Alert Variables Comment by jmontague December 2016
Avatar