As much as time is a constant thorn in my side, both time and timezones are a necessary evil.
Others have outlined some of the issues regarding time zones and the abolishment of them so I won't get into that. What I will say is that time keeping systems generally don't track time in your local timezone. Technology has long since given up on local time as a measurement. Almost all system clocks for computers, phones, pretty much anything electronic, is almost always stored in UTC, or a time code based on UTC.
And I can hear it now, someone saying " but the time on my $thing is $correctlocaltime, which is not UTC"
Yep, and that's where the magic happens. While the time is stored as UTC, it's displayed as local based on your device's time zone settings. In some cases, like with cellphones, the local timezone is set by GPS. The device gets a very very general idea of where you are from GPS, and sets your timezone appropriately. Windows will do this too based on location awareness, by default. I'm sure os x also does something similar.
When the time is displayed it takes the UTC system time and filters it through the UTC offset based on your timezone, and displays local time, factoring in daylight savings, if applicable.
We've silently converted to a single unified time globally, and nobody realizes it has happened because the user interface shows you what you want to see.
At home, libreNMS. Just SNMP everything.
For work, whatever the tool of the day is from management.