[tech] [committee] Temperature Monitoring in Server Room [repost]

[Melissa Star]

Hi James,

> I am explicitly going to leave this for someone else to set up, my 
> recommendation is a new VM, (although you could do a container) since it 
> requires PHP 7.1.3 at a minimum.

Isn't UCC a do-ocracy?

I'm sure there are more standard ways, for example, to dispense drinks or maintain club membership records.

And we could be using Microsoft Word or even OpenOffice to take minutes and SharePoint or perhaps OwnCloud to maintain records.

Except we don't. From what I've seen so far, where possible we use solutions made by UCC members, even if they are not technically superior, because they are ours.

Leaving aside the fact that:

* You turned away from me and left me out of the decision making process that came out of my idea.

* You suggested running system management tools in a VM because that would involve install PHP 7.x on the machine, and we've got stuff running on 5.x (note not all machines at UCC are VM hosts).

* You don't mind us running PHP  5.x with all the resulting security risks


Regards,

Melissa




> 
> On Mon, 18 Mar 2019, Andrew Williams wrote:
> 
>> On 2019-03-18 9:58 PM, David Adam wrote:
>>> On Mon, 18 Mar 2019, Melissa Star wrote:
>>>> I just realised - if you have smartmontools installed on linux machines,
>>>> each hard drive or SSD will provide its “Airflow Temperature”, which I
>>>> can extract via script.
>>>> 
>>>> I'm thinking of centralising this for all the servers I run, and
>>>> collecting the data to chart, having a display at home that gives me
>>>> live info for all machines under my control.
>>> 
>>> We used to do this on all the servers, but I think evil is the only one
>>> still running:
>> 
>> Rather than rolling your own temperature monitoring scripts and code to 
>> display them, I highly recommend installing Nagios/Icinga or equivalent. 
>> That will monitor network services (web, database, NTP, SSH, etc), host 
>> state, disk space, rack and internal temperatures, voltages, fan speeds, 
>> etc, on tens or hundreds of machines.
>> 
>> Here's the Icinga2 setup for the MWA telescope - it's using a mix of 
>> built-in and third-party plugins for the sort of things you'd see in a 
>> normal server room, plus custom plugins to monitor the actual telescope 
>> hardware and software health.
>> 
>> http://icinga.mwa128t.org/icingaweb2/monitoring/list/hostgroups
>> 
>> (username 'guest', password 'mwa-guest')
>> 
>> The performance data (raw values from every sensor or measurement) is 
>> automatically piped from icinga to a Whisper/Carbon backend, and we use 
>> Graphite to view the time series plots:
>> 
>> http://graphite.mwa128t.org/dashboard
>> 
>> You can either go to Dashboard/Finder and choose one of our pre-saved 
>> plot layouts (please don't change them, or save new ones), or drill down 
>> through the monitoring point tree using the top half of the page 
>> (starting with icinga2. then going down through a hostname, then a 
>> service on that host, until you reach a ....value leaf node, and add a 
>> graph showing that value to the dashboard). I usually prefer to use the 
>> Tree interface instead - go to Dashboard/Configure UI, then choose 'Tree 
>> (left nav)'.
>> 
>> Andrew
>> _______________________________________________
>> List Archives: http://lists.ucc.asn.au/pipermail/tech
>> 
>> Unsubscribe here: https://lists.ucc.gu.uwa.edu.au/mailman/options/tech/trs80%40ucc.gu.uwa.edu.au
> 
> 
> -- 
> # TRS-80              trs80(a)ucc.gu.uwa.edu.au #/ "Otherwise Bub here will do \
> # UCC Wheel Member     http://trs80.ucc.asn.au/ #|  what squirrels do best     |
> [ "There's nobody getting rich writing          ]|  -- Collect and hide your   |
> [  software that I know of" -- Bill Gates, 1980 ]\  nuts." -- Acid Reflux #231 /