Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-23968

Audit log hags when Recordset ID filter applied

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • None
    • 6.0.24
    • None
    • None

      Steps to reproduce:

      1. Navigate to Report -> Audit
      2. Click any Recordset ID to apply filter
      3. Wait for it load

      Result:
      In 5 of 10 times after some time there is an error like this:

      Error in query [SELECT a.auditid,a.userid,a.username,a.clock,a.action,a.resourcetype,a.ip,a.resourceid,a.resourcename,a.details,a.recordsetid FROM auditlog a WHERE a.clock>='1703077331' AND a.clock<='1705669331' AND a.recordsetid='clr7tawnb0000iktmx022cxy4' ORDER BY a.auditid DESC LIMIT 1001] [Query execution was interrupted] [zabbix.php:22 → require_once() → ZBase->run() → ZBase->processRequest() → CController->run() → CControllerAuditLogList->doAction() → CApiWrapper->__call() → CFrontendApiWrapper->callMethod() → CApiWrapper->callMethod() → CFrontendApiWrapper->callClientMethod() → CLocalApiClient->callMethod() → CAuditLog->get() → DBselect() → trigger_error() in include/db.inc.php:248]

      Expected:
      Filtred list.

      I guess it depends on size of installation. But can we do some optimization to fronted to mitigate this?

            bmickiewicz Bartosz Mickiewicz
            supaflybro Artem Mizin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: