SpivR 2 Report post Posted July 15, 2017 Any progress on allowing configurable names for custom TCP/IP port monitoring alerts? Today I got a client alert for "Custom TCP Service on user-specified port" and it took me a long time to dig through offline notes to figure out what was supposed to be running on port 8065 of that particular device. If I could name the custom port monitoring to be something like "backup server" then the alert would have been self-identifying. Share this post Link to post Share on other sites
SpivR 2 Report post Posted August 18, 2017 Would appreciate an update on this request. Now that it is extra cost to configure more custom alerts, this is more a “must have” than a “want to have”. If I am going to spend $$ on adding more alerts, SNMP, etc. would need to be able to quickly identify which alerts are being reported in an easier to understand way. Share this post Link to post Share on other sites
