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

Elasticsearch 7.x HTTP status code: 400

XMLWordPrintable

    • Icon: Patch request Patch request
    • Resolution: Fixed
    • Icon: Trivial Trivial
    • 5.0.2rc1, 5.2.0alpha1, 5.2 (plan)
    • 5.0.0
    • Server (S)
    • None
    • Centos 7, x86_64
    • Sprint 64 (May 2020), Sprint 65 (Jun 2020)
    • 0.25

      Steps to reproduce:

      1. Fresh install of zabbix-mysql.
      2. Configure zabbix history save at elasticsearch.

      Result:
      See screenshot Screenshot_20200523_224154.png

      Expected:
      No "HTTP status code: 400" at zabbix_server.log
      See attached patch file zbx50_history_elastic.c.diff

        1. content_length_diff.png
          content_length_diff.png
          1.69 MB
        2. elasticsearch.access.log
          3.40 MB
        3. elasticsearch.error.log
          9.81 MB
        4. Screenshot_20200523_224154.png
          Screenshot_20200523_224154.png
          400 kB
        5. zabbix_patched.png
          zabbix_patched.png
          96 kB
        6. zabbix_server.log
          845 kB
        7. zabbix.pcap
          323 kB
        8. zabbix.png
          zabbix.png
          131 kB
        9. zbx50_history_elastic.c.diff
          0.7 kB

            arimdjonoks Artjoms Rimdjonoks
            pf2012 Pavel Fiyalka
            Team C
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: