www.monitorware.com uses cookies to ensure that we give you the best experience on our website. If you continue to use this site, you confirm and accept the use of Cookies on our site. You will find more informations in our Data Privacy Policy.OkRead more

It parses the data out and hence all of the fields of MonitorWare Database
would be filled.

It is supported by WinSyslog 5.0 Enterprise Edition and MonitorWare Agent
(EventReporter 6.0 will also support SETP sending)

Since MonitorWare Console expects that all of the fields of the database
have some values in it, it generates more meaningful reports with SETP as
compared to Syslog (with which most of the fields are empty)

One thing to keep in mind is that if you are sending the data using SETP
protocol, then on the receiving end there must be a SETP listener to receive that
data. So, in no case it is possible that you send the data using MonitorWare
Agent (which supports SETP sending) and receive that data using WinSyslog 4.x
(which doesn't support SETP receiving).

Please note that the syslog restrictions mentioned here apply to traditional, UDP based
syslog. There are newer syslog standards available, most importantly RFC 3195. Adiscon
is one of the yet few supporters of these
new standards. With it, the reliability issues of syslog are solved. However, there are still
length isuses, so that this is not the final solution. Adiscon is actively working with
the standards bodies to improve syslog protocol's capabilities. We hope that, in the medium to
long term, we can provide the same benefits SETP offers over standardized syslog.