Sorry just to add to this in-case I left out a few details.
When you create a svcrsp test (a plugin to sysedge). You specify the index, The index falls under the main svcrsptable,
.1.3.6.1.4.1.546.16.6.10.1 svcrsptableentry
The table has attributes and OIDS.
The attribute,
Name | svcRspTableErrorCode |
.1.3.6.1.4.1.546.16.6.10.1.39.<+yourindex>
The error code returned by the test. The values are specific to
each test type. When possible, the standard numeric error codes
for each test will be used (e.g. HTTP 404).
So assuming you created a svcrsp for a website under index 53
You could create a monitor OID (see above post) for the 1.3.6.1.4.1.546.16.6.10.1.39.53 with an appropriate operator like not equal 200 to perform the action of email.exe and pass the arguments of who you want to mail, etc... For another test / site you can do the same, for a different site and if needed with the separate arguments for a different email user.
* Just a side note Actions typically occur at every state change so there is usually a script written along with the action to evaluate the automatically passed argument of the trap type. So you may want to take a review of the below tech doc.
* http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1567723.aspx
Hopefully this adds/clarifies my above post.