Collector 27.005 breaks MySQL v5 monitoring

Question

Today we were upgraded to collector version 27.005 and our MySQL monitoring is now broken. I tried to downgrade to 27.000 but the downgrade does not appear to be actioned, even though I can choose the option in Settings > Collectors. Can we please have our MySQL 5 monitoring back, or can you suggest what we need to do. Thanks.

Unknown system variable 'system_time_zone'
Query is : SELECT @@max_allowed_packet , @@system_time_zone, @@time_zone, @@sql_mode

@Ali Holmes

@Sarah Terry

Unknown system variable 'system_time_zone'
Query is : SELECT @@max_allowed_packet , @@system_time_zone, @@time_zone, @@sql_mode

@Ali Holmes

@Sarah Terry

mike_rodrigues · Answer

Hey @Mosh, sorry you had to deal with this. I didn't see a support ticket from you, but you should hear from them or your CSM shortly.
	We're looking at this on our end, I'll update this ticket when I know more.

mike_moniz · Answer

Just to throw it out there, the error kinda looks like a known bug in MySQL pre 5.0.24. Although I wouldn't expect a collector upgrade to trigger it. I don't monitor MySQL to test myself.

https://bugs.mysql.com/bug.php?id=15455

mosh · Answer

Thanks @Michael Rodrigues

Forum Discussion

Collector 27.005 breaks MySQL v5 monitoring

3 Replies

Related Content

Collectors: Open Telemetry vs. LM Collector

Process Monitoring

Bug early release Collector Update V34.500

Stop collector or batshscript queued tasks from collector debug?

Meraki monitoring within Logic Monitor

Recent Discussions

Dashboard Sharing – An Inline Framing Method

2021-12-15 US Office Hours

Live Training - Tuning Datapoints and Alerts - 15th JUNE 2022 - APAC

Live Training - Introduction to Dashboards - 18th MAY 2022 - APAC

2022-05-11- APAC Product Overview -Collectors, Resources/Groups, Dashboards