jdwinns

Comments

  • Has anyone ever ran into formatting issues with these templates? What I mean is, from what I am experiencing, once Outlooks get it's grubby little hands on the HTML, it will occasionally screw with the formatting and change the font, spacing, etc.
  • Does anyone have an example of what their stored procedure looks like for this? I've never set one up, just want to make sure I get it right.
  • We are currently monitoring these Log4j application logs using the SAM Log Parser application monitor template (Powershell/Perl). These are working good but if there is a cleaner way to monitor these logs, I'm definitely up for looking into it. The logs that we are monitoring range in size but mostly between 100MB - 250MB…
  • Very cool! Couple quick questions - Can OLV be integrated with SAM? Also, can we configure this to monitor our application logs, some of which are in Log4j format?
  • Sorry to resurrect this but I am getting the same error. The odd thing is we are running Windows agents on these boxes so why would it be polling with WMI? Same as joe.tran​, the Application monitor (and the template) are set to use Agent polling.
  • Same problem here..
  • Just an update on this - We continue to occasionally receive "No newly found strings" in alert emails from our "Log Parser - Newly Found Strings" applications. It happened today and I quickly verified that the alert was valid by locating the string in today's log. What I still believe might be happening is when the monitor…
  • I just noticed while troubleshooting that our database is out of sync. Not positive if the two issues are related or not. The "No newly found strings" alert issue has been happening on occasion for a few months, the database sync seems to be a newer problem. Has anyone else had this happen or know the reason why the…
  • Has anyone used OpsGenie or Alert Central? I see that AC is discontinued, is anyone still using it in their environment?
  • How important is the position in the "newly found strings" component? I have this running against one of our log files with the position set to 0. For some reason it keeps finding the same "new" strings in our log file. I've cleared the alert, disabled/re-enabled it, still won't clear. Anyone else ever run into this?