Kentix MultiSensor is a device which includes many sensors for use in monitoring server and IT rooms. The sensor only needs to be connected to your network (PoE is required) and to have SNMP configured through its web interface.
The LAN version we used in this test monitors:
Temperature
Humidity
Dewpoint
Fire (carbon monoxide)
Motion
Vibration
More info about threats detected by Kentix Multisensor-LAN can be found in the threat matrix.
This sensor can feed data to NetEye 4 using both SNMP requests, which can be directly polled by Icinga 2, and SNMP traps, which can be collected using the Tornado SNMP Collector. Both SNMP v2 and v3 are supported.
Temperature, humidity, dewpoint and fire can be monitored using the check_snmp script and creating a service set to monitor them.
Motion and vibration instead cannot be periodically polled: these alarms are event-based and therefore checking them once every 5 minutes can easily cause you to miss an intrusion or vibration event. We can overcome this problem by using Tornado’s SNMP collector to filter relevant traps and move a service to critical status in the case of vibration or intrusion events.
Collected values, such as temperature and humidity, can be shown in in an ITOA dashboard:
The capabilities of Kentix’s Multisensor can be extended with their Leakage sensor and Door sensor.
With Elastic Observability we can create alerts on all data we collect, such as logs, metrics, application services and synthetic monitoring. However, NetEye represents the main operational console from which to monitor the entire infrastructure. By sending alarms from Elastic Read More
Node export in the Tornado Processing Tree was broken on Firefox The bug was caused by a divergence between Firefox and Chrome in blob handling with CSP. Issue resolved, behavior is now consistent across both browsers. List of updated packages Read More
Processing Tree Rendering Issue We shipped a fix for a rendering bug in the Tornado UI Processing Tree. Under specific conditions, navigating back to the dashboard after expanding tree nodes caused the tree to render incorrectly nodes would appear collapsed, Read More
Running Ollama locally or on dedicated hardware is straightforward until you need to know whether a model is actually loaded in RAM, how fast it generates tokens under load, or when memory consumption reaches a threshold that affects other workloads. Read More
Hello to you all. It's been a while. Don't worry though, this won't be a long and technical post. It's just to let you know I'm doing (almost) well and to tell you about our latest news. The Metrics Challenge Read More