Garbled binary junk in alert_log table?

# /opt/librenms/validate.php
====================================
Component | Version
--------- | -------
LibreNMS  | 1.45-14-g4e8acdd
DB Schema | 270
PHP       | 7.0.32-0ubuntu0.16.04.1
MySQL     | 10.0.36-MariaDB-0ubuntu0.16.04.1
RRDTool   | 1.5.5
SNMP      | NET-SNMP 5.7.3
====================================

[OK]    Composer Version: 1.7.3
[OK]    Dependencies up-to-date.
[OK]    Database connection successful
[OK]    Database schema correct
[WARN]  IPv6 is disabled on your server, you will not be able to add IPv6 devices.
[WARN]  Your local git contains modified files, this could prevent automatic updates.
        [FIX]:
        You can fix this with ./scripts/github-remove
        Modified Files:
         misc/macros.json
If it's an issue with the WebUI then please consider including a screenshot and the browser version you are using.

I am trying to do some queries again my database to get some info about alerts, but there’s unprintable junk in some of the entries that breaks my terminal and prevents me from searching through alert details:

   MariaDB [librenms]> select * from alert_log where time_logged between '11/01/2018' and curdate() limit 5\G
*************************** 1. row ***************************
         id: 5506
    rule_id: 3
  device_id: 14
      state: 0
    details: xګV▒▒+I-*K▒Q▒245▒▒45673▒ [▒▒
time_logged: 2017-11-06 00:30:51
*************************** 2. row ***************************
         id: 5507
    rule_id: 3
  device_id: 14
      state: 1
    details: x▒]▒MO▒ ▒▒J3▒▒▒▒▒▒d▒'▒▒fC▒Klit▒6▒▒▒uMX▒▒</3▒a▒w f▒M▒▒}▒ݩ▒▒t▒▒잷▒▒`▒A▒▒▒|o▒;td▒W▒B▒g▒▒▒▒e:]t▒▒{d▒ip
'y▒5▒"I▒h▒l▒▒▒▒h"       GBH▒▒▒▒6▒69eE▒)Y▒▒▒uPd▒;\G▒%'$▒▒▒&▒G▒kIN        ▒▒E▒▒ju▒;|Jk▒▒▒▒▒Z▒N,o)h▒ўe
                                                                                                   ▒▒▒eX2I▒O▒▒▒▒ yR▒r
time_logged: 2017-11-06 00:40:23
*************************** 3. row ***************************
         id: 5508
    rule_id: 3
  device_id: 14
      state: 0
    details: NULL
time_logged: 2017-11-06 01:02:17
*************************** 4. row ***************************
         id: 5509
    rule_id: 3
  device_id: 14
      state: 1
    details: x▒]▒▒N▒ ▒_▒▒sc▒-▒p2Y▒ɬ▒=▒▒▒v▒%▒▒▒V▒}w▒&▒▒▒▒~▒
▒@3▒▒@.▒▒^▒▒Z▒▒0▒▒z▒▒}▒▒9;▒e▒▒▒q▒▒ ▒▒C
-▒ts%▒/▒▒:▒▒▒֑Ѧ▒9▒,b▒k▒K|▒
                         ▒▒vQ▒E▒▒▒▒▒p▒'Uc'▒d▒V▒.▒N}▒6▒▒
▒▒F▒▒^{g▒ʳ▒(*V▒▒NF▒_ 7▒▒:R▒▒,/J▒▒,▒-EF3'▒6▒+▒▒▒Nnf▒▒_^"p~KA▒:▒▒!▒8Mæ&▒:▒ {▒▒x
time_logged: 2017-11-06 01:05:42
*************************** 5. row ***************************
         id: 5510
    rule_id: 3
  device_id: 14
      state: 0
    details: NULL
time_logged: 2017-11-06 01:11:02
5 rows in set, 1 warning (0.00 sec)

Any idea what might cause this? Is it some kind of character set or encoding mismatch? Any help much appreciated, let me know what other info I can provide.

It’s gzipd + compressed in php.

You need to get the data out and run json_decode(gzuncompress()) on the result