The STALL data filter

Currently, Kronometrix, is supporting two types of raw data filters: the STALL and RANGE filters.

A raw data filter is a mechanism to ensure that incoming raw data follows certain rules or conditions before the numerical processing and data visualization, within Kronometrix. For example the STALL filter will ensure raw data is properly arriving to our appliance and there are no delays. The RANGE filter, will ensure incoming raw data is sane and valid, and stays within certain range of values. For example the air temperature is valid as long as it is between -50C to 50C or the CPU Utilization of a Windows server is between 0 and 100%.


The STALL Filter

Defined under messages.json and part of the Library of Monitoring Objects, the STALL filter is part of the data message definition. For example this is the way to define the STALL for a data message, called sysrec, which belongs to a data source type: Linux (a computer system running Linux CentOS operating system). 

stall: seconds

The STALL filter, is defined in seconds, describing the time spent before triggering a STALL warning under Kronometrix event management console:



Turn them off

Starting with Kronometrix 1.2 we are able to turn ON/OFF, per subscription the STALL detector. That means if we have several data subscriptions, we can say for what subscriptions the filter should be ON or OFF, no matter what the messages.json will have configured.

See here:



dcsim and mix subscriptions require some updates, some computer systems will need some maintenance work and during this period of time we dont want to receive warnings and alerts from any sources which belong to these two subscriptions. So we turned OFF the STALL filters for these two subscriptions.


Why STALL filter is important and you should use it

  • because we want to see and get notified when we are not receiving data from sensors, computer hosts, weather stations, etc
  • we want to keep a close look how often data is missing or is delayed
  • because we are forced by regulations and laws to monitor and report these delays (example, Airports, Air Traffic Controller)

Comments

Post a Comment

Popular posts from this blog

Asus Zenbook and FreeBSD 11

Image
This is a short description how I got running FreeBSD 11-current on my Asus Zenbook UX32VD laptop. Im very happy with the current setup but of course it is room for improvements in many areas. Having DTrace, ZFS and the other goodies makes FreeBSD a real good candidate for a mobile environment. Last Updated: 16 March 2015 Zenbook UX32VD Configuration CPU: Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz Memory: 6 GB RAM Storage: SanDisk SSD i100 24GB, Samsung SSD 840 PRO 500GB Video: Intel HD Graphics 4000, Nvidia GT620M Display: 13" IPS Full HD anti-glare Wifi: Intel Centrino Advanced-N 6235 3 x USB 3.0 port(s)  1 x HDMI  1 x Mini VGA Port  1 x SD card reader Note: The laptop's internal hard drive, has been replaced by a Samsung SSD.
Read more

Raspberry Pi and Redis

Image
This summer we did something amazing: we took our enterprise appliance, a very powerful server and we tried to run same software, same analytic kernel and all the other things in something smaller and lot simpler, like this: Light, mobile appliance And we did it ! Being powered by OpenResty and Lua we were able to size our appliance easily and be up and running quickly. Low factor, low power consumption, very cheap, these ARM based devices are getting more and more attention and become more popular nowadays: Banana Pi - A Highend Single-Board Computer 4 x Raspberry Pi + Arduino = UDOO What ? Analytics on a Raspberry PI ... !? Yep. First of all, we wanted to experiment with ARM based boards using few number of hosts and few data messages per host as input. The immediate trouble was that we should fit in 512MB RAM with all our software and customer data. Then these boards don't run on latest Intel specs but something like 700 Mhz CPU as a system on chip wi
Read more

Web Performance, tell me the story

Image
Suppose you would like to know how your web site, behaves to clients from two different geo locations: for example, Finland and Ireland regarding response time. How quickly can you see and understand visually what's going on and how things are. Do you need to improve something ? Change your network provider ? Tune your application(s) ? Spend more money.  Start from a top level view, understanding the big picture and having the possibility to dive and analyze at the detail level.  Finally, can you visually tell the story of your web application as in a short chart ? Enter Kronometrix Web Performance ... Finland Something happened between 1:00 - 1:15 AM We can see more than one request affected by this event Overall we see all requests are executing fast, below 0.5 seconds And we have some exceptions, some are taking more than 0.5 seconds Ireland Same things from Ireland It is different, requests usually take longer to execute
Read more