Alerts, syslog, and command triggers

Started by Chico


Alerts, syslog, and command triggers   17 October 2020, 19:28


I'm currently trying NetMaster in my little lab-network.
It seems like a nifty little tool at a reasonable price.
(But please consider a Dark Mode setting, as I mentioned in another post).

My question is: Do you on your roadmap have plans for some simple alerting mechanism?
For example:
1. Logging alerts (new processes connecting and such) to a syslog server from each computer running the service.
2. Trigger a command line on alert.
I prefer that over email-alerting as the only option because it is easy to set up sending of email on alert via the command line. The lack of alerting is my major reason for not considering NetMaster right now. Preferably, alerting should be possible to set from one console to every machine, even if the target machine only runs the service.

By the way, major, major kudos to you for having a forum that does not require registration! A lot more companies should follow your example.
Have a nice day.

SoftPerfect Support forum - Andrew avatar image

Re: Alerts, syslog, and command triggers   18 October 2020, 14:13

Thank you for your feedback. Unfortunately we are not planning to implement any kind of alerts, especially syslog. The reason for that is two-fold:
  1. NetMaster core runs as a service. It has no user interface to display those alerts when they occur.
  2. Syslog is something from the Unix world, and an average user would have no idea what it is or how to use it.

We would like to keep NetMaster as simple and as user-friendly as possible, and only add essential features. If you really need syslog, you could use a script launched at periodic intervals that would analyse the database and send the events to a syslog server.

Reply to this topic

Sometimes you can find a solution faster if you try the forum search, have a look at the knowledge base, or check the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • Write in English. If possible, check your spelling and grammar.




A brief and informative title for your message, approximately 4–8 words:


Spam prevention: please enter the following code in the input field below.

  ******   ********         **   ******   **     ** 
 **    **  **     **        **  **    **  **     ** 
 **        **     **        **  **        **     ** 
 **        **     **        **  **        **     ** 
 **        **     **  **    **  **        **     ** 
 **    **  **     **  **    **  **    **  **     ** 
  ******   ********    ******    ******    *******