With this bugfix release, we changed telegraf configuration which was causing data loss and delay of data visualization in grafana. We added missing ciphers in the nats-server ‘s TLS configuration for WIN2012R2 and added satellite-log conf for monitoring satellite-master errors. For NetEye 4.20 we updated the following packages: nats-server, nats-server-autosetup to version 2.5.0_neteye1.15.4-1 telegraf, telegraf-autosetup…
Read MoreAs a NetEye user I might want to install a Remote Host Agent that belongs to a Zone that can’t communicate directly with the Master. So to be able to do this, we decided to use Tornado and NATS. Linking with Patrick’s article in this article I’ll explain how to configure them. What we want…
Read MoreWe introduced an interesting new feature into NetEye starting in version 4.13 that permits integrating vSphereDB with Tornado. By being able to process vSphereDB Events and Alarms with Tornado rules and actions, you can for example use vSphereDB to dynamically monitor Virtual Machines and Hosts. Architecture Finding a way to send Alarms and Events stored…
Read MoreIn a previous post we talked about how in NetEye we migrated all the Tornado communications from direct TCP to NATS. Since then, we’ve extensively and successfully adopted NATS as a communication channel for many of the components present in NetEye. As often happens when approaching new technologies, the initial straightforward approach did not turn…
Read MoreUntil the NetEye 4.10 release, the Tornado module inside NetEye handled communications between its components (the Tornado Collectors and the Tornado Engine) via direct, clear-text TCP connections. On local systems, this configuration does not represent a limitation, since in this case there is no requirement to verify the identity of the peer (it is always…
Read More