I do a check for a listen port and then a trigger on this item
this is the mail i get when it gets triggered
Trigger: SQL Server not listening on port 1433
Trigger status: PROBLEM
Trigger severity: Average
Trigger URL:
{TRIGGER.DESCRIPTION}
Item values:
1. SQL Listening on 1433 (xxx:net.tcp.listen[1433]): 1
2. SQL Listening on 1433 (xxx:net.tcp.listen[1433]): 1
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
The graph show all 1's for this item
This is my trigger
{xxx:net.tcp.service[tcp,,1433].last(#1)}#1 & {xxx:net.tcp.service[tcp,,1433].last(#2)}#1
so i check for the last and the one before ... not by time but by actual reads
I am not sure why I am getting this ? Now the backups start around 6pm .. they might be introducing some lag.. but I don't think this is affected by that !
When i look at last data its 1 and when i look at triggers for that server on that page there is nothing !
this is the mail i get when it gets triggered
Trigger: SQL Server not listening on port 1433
Trigger status: PROBLEM
Trigger severity: Average
Trigger URL:
{TRIGGER.DESCRIPTION}
Item values:
1. SQL Listening on 1433 (xxx:net.tcp.listen[1433]): 1
2. SQL Listening on 1433 (xxx:net.tcp.listen[1433]): 1
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
The graph show all 1's for this item
This is my trigger
{xxx:net.tcp.service[tcp,,1433].last(#1)}#1 & {xxx:net.tcp.service[tcp,,1433].last(#2)}#1
so i check for the last and the one before ... not by time but by actual reads
I am not sure why I am getting this ? Now the backups start around 6pm .. they might be introducing some lag.. but I don't think this is affected by that !
When i look at last data its 1 and when i look at triggers for that server on that page there is nothing !