As it should be for a good monitoring system, NetEye has its environmental sensors (smoke-, temperature-, humidity-, water- and more), so why looking elsewhere instead of using your existing solution? NetEye for this purpose provides a configurable box, which can be populated with either 4 or 12 sensors. The box is connected via Ethernet cable to the network and can be then configured.
The “Netsensor” Profile, provided in the NetEye Monitoring, can be used to query the values of the Ethernet Box.
The Ethernet Box is configurable regarding IP settings and sensor availability.
NetEye is already providing a predefined Host + Service profile, which can be assigned to the Ethernet Box.
The sensors indicate exceeded thresholds
They are also showing the continuous state of the values.
How and where can this solution be used?
Application examples:
Temperature sensor:
Detection of a temperature rise in the server room (may indicate a malfunction of the cooling system)
Detection of a temperature rise in the reefer (may indicate that someone forgot to close the door)
Contact sensor:
Detection of an unclosed door (root cause analysis for temperature rise)
Detection of an intrusion or an unauthorized access
Smoke sensor:
Detection of smoke emission
Water sensor:
Detection of a water leak
As you can see, there are many possible applications for environmental monitoring through sensors. The fact, that NetEye also can manage several of these boxes, gives the user the possibility to create a complete image of the facilities he has to monitor.
Hi, I’m Patrick.
Since I was a little boy i love to diassemble and reassemble things...
So I did with my first 386SX back in the 80s... and I still do with my i7 up till now.
I worked in the Service Desk then grew up to a DBA and work now as Integration Consultant at Würth Phoenix.
Author
Patrick Agreiter
Hi, I’m Patrick.
Since I was a little boy i love to diassemble and reassemble things...
So I did with my first 386SX back in the 80s... and I still do with my i7 up till now.
I worked in the Service Desk then grew up to a DBA and work now as Integration Consultant at Würth Phoenix.
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
Role Search Now Works in Access Control We've fixed the search functionality in the Roles view under Configuration - Access Control, so you can now find roles instantly without any errors. List of updated packages To solve the issues mentioned Read More
Hi everyone! Today I'd like to share with you an investigation we undertook related to ingesting Open Telemetry data in Elasticsearch, while maintaining tenant segregation from start to end. The Scenario Let's imagine we have multiple customers, where in this Read More