thewerd

Comments

  • The problem is entirely with the ${NodeID} variable in the statement, and how Orion parses it when sending out an HTML advanced alert it would seem. As the statement as-is works in plain text, and if the variable is removed, and statically replaced with it's node ID value, it also works. ${SQL:Select…
    in Alert not working in HTML Comment by thewerd July 2011
  • I'd love to see this make it in as well. An auditing trail would be a very valuable feature.
    in Tracking who acknowledged alerts Comment by thewerd September 2011
  • I wish. I tried the same as well, no dice. It feels a lot like a parsing bug in Orion for HTML Advanced alerts, since the exact same statement works fine in plain text, instead of HTML. I was hoping there might be a way to get around that, by structuring the query differently, or something. I'm at a loss.
    in Alert not working in HTML Comment by thewerd July 2011
  • Yeah. If I run the query directly on the database and remove ${NodeID} and replace it with the correct appropriate number, it returns the correct result. If I do the same in the alert itself (replacing ${NodeID} with the actual node number, it also properly spits out the correct result.
    in Alert not working in HTML Comment by thewerd July 2011
Avatar