Service UP/Down and emails

[Rabid]

I am testing out NetXMS and so far I like it.  I do have a couple of questions.  I have set up a DCI for a random service.  This part works.  0 for service is running and 6 for service is down.  Under Thresholds for this DCI I have added one threshold with the following settings:

last polled value
1 samples
will be equal to 6

if true "sys_service_down"
when becomes false "sys_service_up"

use default settings

Under actions I created two new actions.  One is Service Down set to email me.  One is called Service Up which is also set to email me.

Under the Event Processing Policy for the event "sys_service_down/sys_service_unknown" I added the action service down (the action to email me).

Under the Event Processing Policy for the event "sys_service_up" I added the action service up (the action to email me).

When the service goes down, I get a red dot to the side of the node and I get my service down email.  When the service goes back up the red dot goes away and I do NOT get an email. 

I have two questions.  First how do I get NetXMS to email me once the service comes back up.  Second, instead of having the event go into the master event log, how do i get it to show up under the alarm for that node?  I have looked in the manual and there doesnt appear to be any examples.  Any help would be appreciated.

Will there be reporting any time in the future?

[Rabid]

Seems the Up email works now.  I guess I didnt save it.  Now my only question is about having the alarms show up under the alarms tab for the node, instead of the master event log.

Another question, if a node goes offline and I am monitoring 20 services, will i get an email on each one?  Or is there a way to make the 20 monitored services dependant on the node being up?

Thanks

[victor]

Because you are monitoring services using DCIs, you will not get service down events in case of entire node down, because there will be no new values for DCI, and therefore no events will be triggered. Btw, it is not recommened to use SYS_xxx events in thresholds - they are generated by server in various situations, and you can get unexpected results. SYS_SERVICE_DOWN and SYS_SERVICE_UP generated by server during status poll of network services. Until you are not using network service objects, you are fine, but if you eventually configure some, you will get unexpected events. Better approach is to create your own events.

Best regards,
Victor