Skip to main content

monitoring and reporting interview

Q: Is there a monitoring and reporting tool package that can do "everything"?

A: Depending on the application. Well, speaking on past experience, I haven't seen a tool that has just out of the box done all the monitoring and reporting you will ever need. Uptime, performance or disk space alerts probably, but once you get down to the application you need to support, you're on your own and will need to build your own interface to the package or alert system.

Q: What about mature software packages by big vendors that have complicated specifications and requirements.

A: Some of these are great tools that work in specialised enviornments. Each tool will work on a case by case basis. Policy is currently an organisations best friend in controlling this enviornment. It can dictate what computer hardware and software are used. However in real life, its very difficult to maintain a certain standard as everyone works differently and you will obviously get the renegade department or people who will do something else and making them comply to standards is not a method of increasing productivity.

When you find a monitoring system that sounds too good to be true, it probably isn't true. Always implement a proof of concept and determine the measures of success first.

Q: What are the measures of sucess of system monitoring and reporting?

A: 100% of system managers will say if the business need is met. Thats just an easy answer because its vague and easy to get away with. After all, who is going to challenge "business need"? A chalenge of determining a success of a system is normally in determining the metrics and thresholds. Since monitoring and reporting are already metrics, success factors are already determined. How easy is that?

I'd work through this process with the example of recording a track, as there is always more than one method. Laying the drums is normally the most basic and un-inspirational. Using an appagiator kicks of some imagination, but gets monotonous. These are the easiest methods. drum == server metrics, apagiator == third party tools. You get a solution but is it what you need?

Q: What makes the best "track" or solution?

A: I feel that the best track normally comes from the inspired player. It doesn't happen often and thats probably why there aren't that many best tracks around. How this equates to system and reporting is that the designer already knows what he or she wants. An apple hitting the head, or falling in the bathroom (kids do not do this at home). After knowing what you want, just go out and get or build the thing that you need.

Sounds way to tough, but dig deep and find that the answer is always simple. That determines the best solution for you. Do not fret if its not like what other packages are like. As long as it works for you and your organisation.

About the interviewee; pipsqueak has been designing monitoring, reporting and alert systems in various projects accross different servers both with and without cash from management.


Popular posts from this blog

Multiple Broadlink RM mini 3 integration using MQTT

Broadlink now has quite a lot of integration options almost out of the box. If you enable Broadlink IHC, you can directly link it to Alexa by giving the device a unique name.

There is a homebridge plug in for homekit integration but I haven't tried or tested this.

I wanted to put the device in domoticz so I can have more control over what can trigger my broadlink. I decided to use broadlink-mqtt for this, which is a fairly easy method to trigger from any source.

Setup Instructions for broadlink-mqtt

1. git clone

2. vi /home/pi/broadlink-mqtt/mqtt.conf

3. Update the mqtt.conf file with the device type set as multiple_lookup

device_type = 'multiple_lookup'
mqtt_multiple_subprefix_format = '{type}_{mac_nic}/'
4. Start the python script and check that it started and detected all the RM devices.
Check the log file to see what the IP / MAC addresses are. DEBUG Connected to RM2 Broadlink device at …

Fibaro HCL Virtual Device Slider

How to setup Fibaro home center lite (HCL) slider for virtual devices.

As the Fibaro HCL does not support LUA. The question was how to update the number value of the slider to send to the HTTP string. Thanks to this site which is a really good reference

The 2 use cases here are;

Sonos HTTP API Volume

To allow for volume control for all Sonos devices, add a virtual device with the IP address for SONOS HTTP API and specify the default port to 5005. Create Slider and put the following text into the string.

GET /volume/_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Domotiz Virtual Devices

GET /json.htm?type=command&param=switchlight&idx=XX&switchcmd=Set%20Level&level=_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Replace XX with the device ID.

Restart Fibaro HCL when it stops working automatically

It seems that the Fibaro HCL seems to hang every now and then. Instead of trying to restart it regularly, which doesn't really work, as it's almost impossible to predict when this will happen.

This method checks that the HCL is actually running and in the event it stops working, trigger a script that will restart it.

1. Get a non Fibaro controlled power plug and scripts to control it.

I used a wifi smart plug, TP-link HS100 and downloaded the scripts from

2. Create a bash script to restart the Fibaro, e.g.



$scripts/ -t $ip_addr -c off
sleep 10
$scripts/ -t $ip_addr -c on

3. Create a test global variable in the Fibaro HCL

Go to the variables panel and create a test variable, e.g. Test

4. Add a cron entry to test that the Fibaro API is still working and restart if it's not.

The cron script is scheduled ev…