Template became not supported: Unsupported item key. #1

r0039 · 2019-02-27T08:24:51Z

Hi,

I hope you are still working on this git release. I am having an issue with my system. Hope I can receive any feedback from you to fix it.

My system:

Graylog 3.0
Zabbix 4.0
Python 3.5
Ubuntu 16.04 LTS

I tightly followed your instruction, however, this is not the same version of Zabbix and Python, then I got any issue [not supported] with following templates:

GrayLog: Filter execution Time(FIltered OutMessages) 5min
GrayLog: Filter execution Time(Incoming Messages) 5min
GrayLog: Filter execution Time(Outgoing Message) 5min
GrayLog: Filter execution Time(Process Time) 5min
GrayLog: Internal Log Message Error 5 min
GrayLog: Internal Log Message Fatal 5 min
GrayLog: Internal Log Message Trace 5 min
GrayLog: Internal Log Message Warn 5 min
GrayLog Journal Size

Here is the error

item "graylog-srv-02:graylog.proc.buffer[ProcessBufferProcessor.processTime,m5_rate]" became not supported: Unsupported item key.

Could you please help me fix it? Thank you so much!

r0039 · 2019-02-27T08:33:56Z

Also I provide what did I implement?

sky@zabbix4-srv-01:/opt/packages$ sudo git clone https://github.com/bezarsnba/zabbix-graylog-monitoring.git
sky@zabbix4-srv-01:/opt/packages$ cd zabbix-graylog-monitoring/
sky@zabbix4-srv-01:/opt/packages/zabbix-graylog-monitoring$ sudo mkdir /etc/zabbix/scripts
sky@zabbix4-srv-01:/opt/packages/zabbix-graylog-monitoring$ sudo chmod +x /etc/zabbix/scripts/monitoring-graylog.py

sky@zabbix4-srv-01:/etc/zabbix/scipts$ python3
python3     python3.5   python3.5m  python3m
sky@zabbix4-srv-01:/etc/zabbix/scipts$ python3.5 monitoring-graylog.py lldgraylognode
{
    "data":[
        {
            "{#NODEID}":"74654950-8fa7-4b2f-ac1f-afe08d2d1b02"
        }
    ]
}

sky@zabbix4-srv-01:/etc/zabbix/scipts$ grep Include /etc/zabbix/zabbix_agentd.conf
### Option: Include
# Include=
Include=/etc/zabbix/zabbix_agentd.d/*.conf
# Include=/usr/local/etc/zabbix_agentd.userparams.conf
# Include=/usr/local/etc/zabbix_agentd.conf.d/
# Include=/usr/local/etc/zabbix_agentd.conf.d/*.conf

sky@zabbix4-srv-01:/etc/zabbix/scipts$ sudo cp /opt/packages/zabbix-graylog-monitoring/user_parameter_graylog.conf /etc/zabbix/zabbix_agentd.d/

sky@zabbix4-srv-01:/etc/zabbix$ zabbix_get -s 10.30.3.117 -k graylog.discovery.node
{
    "data":[
        {
            "{#NODEID}":"74654950-8fa7-4b2f-ac1f-afe08d2d1b02"
        }
    ]
}

sky@zabbix4-srv-01:/etc/zabbix/zabbix_agentd.d$ zabbix_get -s 10.30.3.117 -k graylog.cluster.status['74654950-8fa7-4b2f-ac1f-afe08d2d1b02',lb_status]
alive

r0039 · 2019-02-28T02:50:58Z

hi @bezarsnba could you please help me on this issue? Thank you so much!

bezarsnba · 2019-02-28T18:05:34Z

Hi @r0039 at moment we didn't test the items on Graylog 3.0 only 2.4, I go to test and to verify the error.

bezarsnba · 2019-02-28T18:31:32Z

Hi @r0039 , Can do you a test? Of your Zabbix Server run this command:

zabbix_get -s -k graylog.proc.buffer[ProcessBufferProcessor.processTime,m5_rate]

Thanks

r0039 · 2019-03-01T02:54:31Z

I am glad to receive your message @bezarsnba !!!

Help you investigate fastly, I show my topology:

Graylog server: 10.30.3.118
Zabbix server: 10.30.3.117

With your command, I did run as below:

sky@zabbix4-srv-01:~$ zabbix_get -s -k graylog.proc.buffer[ProcessBufferProcessor.processTime,m5_rate]
usage:
  zabbix_get -s host-name-or-IP [-p port-number] [-I IP-address] -k item-key
  zabbix_get -s host-name-or-IP [-p port-number] [-I IP-address]
                --tls-connect cert --tls-ca-file CA-file
                [--tls-crl-file CRL-file] [--tls-agent-cert-issuer cert-issuer]
                [--tls-agent-cert-subject cert-subject]
                --tls-cert-file cert-file --tls-key-file key-file -k item-key
  zabbix_get -s host-name-or-IP [-p port-number] [-I IP-address]
                --tls-connect psk --tls-psk-identity PSK-identity
                --tls-psk-file PSK-file -k item-key
  zabbix_get -h
  zabbix_get -V

Then, I added the host-name-or-IP

sky@zabbix4-srv-01:~$ ifconfig | grep 10.
          inet addr:10.30.3.117  Bcast:10.30.3.255  Mask:255.255.255.0
          collisions:0 txqueuelen:1000

sky@zabbix4-srv-01:~$ zabbix_get -s 10.30.3.117 -k graylog.proc.buffer[ProcessBufferProcessor.processTime,m5_rate]
0.01342501439436139

sky@zabbix4-srv-01:~$ zabbix_get -s 10.30.3.118 -k graylog.proc.buffer[ProcessBufferProcessor.processTime,m5_rate]
zabbix_get [15110]: Check access restrictions in Zabbix agent configuration

Please let me know what can I do to help you find out. I am always welcoming.

r0039 · 2019-03-01T09:37:38Z

I don't know if you are still working on the weekend? 🙆‍♂️
I am waiting for your information about this issue. Thank you for your time ! and your contribution @bezarsnba !

r0039 · 2019-03-04T03:03:16Z

@bezarsnba have a nice week! I hope you can arrange the time to fix this issue. I am using it in my infrastructure and really appreciate your help. Thank you.

bezarsnba · 2019-03-05T02:20:15Z

Hi @r0039 Sorry to the delay, how is the configuration of the host in the Zabbix, do you configured the IP 10.30.3.117?
Because in your test, it's ok to 10.30.3.117

r0039 · 2019-03-05T03:22:25Z

hi @bezarsnba the configuration of zabbix agent declared 10.30.3.117 in Server item.
Server=127.0.0.1,10.30.3.117,10.30.3.118

Also I would like to provide my configuration:

Zabbix Server:
sky@zabbix4-srv-01:~$ sudo vim /etc/zabbix/zabbix_agentd.conf
Server=127.0.0.1,10.30.3.117,10.30.3.118
ServerActive=127.0.0.1

Graylog Server:
sky@graylog-srv-02:~$ vim /etc/zabbix/zabbix_agentd.conf
Server=10.30.3.117
ServerActive=10.30.3.117

And I wanted to monitor Graylog what already installed at server 10.30.3.118.

Please let me know to help your debugging.

r0039 · 2019-03-05T03:24:40Z

also only GrayLog Processes and Service Status are working fine.

bezarsnba · 2019-03-05T19:21:49Z

In your zabbix_server.log, have some error message to the items not supported? If yes, can you send to me the output error? please.
Thanks

bezarsnba · 2019-03-05T22:16:14Z

Could you send the user_parameter_graylog.conf? Please

r0039 · 2019-03-07T04:05:17Z

@bezarsnba sorry for late reply.

Here is zabbix_server.log:
item "graylog-srv-02:graylog.proc.buffer[ProcessBufferProcessor.processTime,m5_rate]" became not supported: Unsupported item key.

and here is user_parameter_graylog.conf

UserParameter=graylog.node.men[*],/usr/bin/python3 /etc/zabbix/scripts/monitoring-graylog.py monnode $1 $2
UserParameter=graylog.cluster.status[*],/usr/bin/python3 /etc/zabbix/scripts/monitoring-graylog.py moncluster $1 $2
UserParameter=graylog.inter.log[*],/usr/bin/python3 /etc/zabbix/scripts/monitoring-graylog.py monmetric $1 $2
UserParameter=graylog.journal.size[*],/usr/bin/python3 /etc/zabbix/scripts/monitoring-graylog.py monmetric $1 $2
UserParameter=graylog.proc.buffer[*],/usr/bin/python3 /etc/zabbix/scripts/monitoring-graylog.py monprocessbuffer $1 $2
UserParameter=graylog.discovery.node,/usr/bin/python3 /etc/zabbix/scripts/monitoring-graylog.py lldgraylognode

Thank you so much :-)

bezarsnba · 2019-03-07T04:24:42Z

Could you send the value of option "Timeout" that is on zabbix_agentd.conf ?. Run this command on graylog to get this information
grep Timeout /etc/zabbix/zabbix_agentd.conf

r0039 · 2019-03-07T05:37:48Z

@bezarsnba Timeout is commented. So do I need to uncomment?

sky@graylog-srv-02:~$ grep Timeout /etc/zabbix/zabbix_agentd.conf
### Option: Timeout
#	Spend no more than Timeout seconds on processing
# Timeout=3

r0039 · 2019-03-07T06:38:14Z

Also I have uncommented and updated the Timeout=3, then Timeout=5, but nothing to changed.

sky@graylog-srv-02:~$ sudo sed -i 's/Timeout=3/Timeout=5/' /etc/zabbix/zabbix_agentd.conf
sky@graylog-srv-02:~$ grep Timeout /etc/zabbix/zabbix_agentd.conf
### Option: Timeout
#	Spend no more than Timeout seconds on processing
Timeout=5
sky@graylog-srv-02:~$ sudo systemctl restart zabbix-agent.service

r0039 · 2019-03-11T02:42:28Z

hi @bezarsnba have a nice week ahead! Hope you can arrange your time for this issue on this week. Thank you so much :-)

r0039 · 2019-03-14T03:23:38Z

@bezarsnba i hope you can let me know some advices what I can do. Thank you.

r0039 · 2019-03-19T09:24:07Z

@bezarsnba I did try it but still could not solve. Hope you have time to see this. Thank you.

yoder731 · 2020-02-17T19:27:16Z

@bezarsnba I am also experiencing issues with items in this template being unsupported. I've gone through most of what you and r0039 have been working on and made any changes where necessary.

It seems that most Zabbix Templates for Graylog have not been touched since Graylogs latest major release.

EmPRio93 · 2020-02-18T13:31:27Z

@bezarsnba I am also experiencing issues with items in this template being unsupported. I've gone through most of what you and r0039 have been working on and made any changes where necessary.

It seems that most Zabbix Templates for Graylog have not been touched since Graylogs latest major release.

I had the same issue
Is your graylog is behind nginx revers proxy?
I have found that graylog API is not always working fine behind proxy. Try to look this way.

yoder731 · 2020-02-18T16:28:34Z

@EmPRio93 Graylog is not behind a proxy. I've got a three node setup with the two slave nodes running elasticsearch. Until someone with more knowledge than I have picks this back up, I am not sure there is anything else I can do.

michalsarna · 2020-09-14T12:47:01Z

Go to file monitoring-graylog.py and edit first line or can replace it with
#!/usr/bin/python3

Then go to user_parameter_graylog.conf and change it to look like:
UserParameter=graylog.node.men[*],/etc/zabbix/scripts/monitoring-graylog.py monnode $1 $2 UserParameter=graylog.cluster.status[*],/etc/zabbix/scripts/monitoring-graylog.py moncluster $1 $2 UserParameter=graylog.inter.log[*],/etc/zabbix/scripts/monitoring-graylog.py monmetric $1 $2 UserParameter=graylog.journal.size[*],/etc/zabbix/scripts/monitoring-graylog.py monmetric $1 $2 UserParameter=graylog.proc.buffer[*],/etc/zabbix/scripts/monitoring-graylog.py monprocessbuffer $1 $2 UserParameter=graylog.discovery.node,/etc/zabbix/scripts/monitoring-graylog.py lldgraylognode

This solved almost all my problems

starinasid · 2023-03-17T10:58:43Z

it dont wokr on zabbix version 5.0 and Graylog 4.2
Error: Unsupported item key.
Do you have any idea?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Template became not supported: Unsupported item key. #1

Template became not supported: Unsupported item key. #1

r0039 commented Feb 27, 2019

r0039 commented Feb 27, 2019 •

edited

Loading

r0039 commented Feb 28, 2019

bezarsnba commented Feb 28, 2019

bezarsnba commented Feb 28, 2019

r0039 commented Mar 1, 2019 •

edited

Loading

r0039 commented Mar 1, 2019

r0039 commented Mar 4, 2019

bezarsnba commented Mar 5, 2019

r0039 commented Mar 5, 2019 •

edited

Loading

r0039 commented Mar 5, 2019

bezarsnba commented Mar 5, 2019 •

edited

Loading

bezarsnba commented Mar 5, 2019

r0039 commented Mar 7, 2019

bezarsnba commented Mar 7, 2019 •

edited

Loading

r0039 commented Mar 7, 2019 •

edited

Loading

r0039 commented Mar 7, 2019 •

edited

Loading

r0039 commented Mar 11, 2019

r0039 commented Mar 14, 2019

r0039 commented Mar 19, 2019

yoder731 commented Feb 17, 2020

EmPRio93 commented Feb 18, 2020

yoder731 commented Feb 18, 2020

michalsarna commented Sep 14, 2020

starinasid commented Mar 17, 2023 •

edited

Loading

Template became not supported: Unsupported item key. #1

Template became not supported: Unsupported item key. #1

Comments

r0039 commented Feb 27, 2019

r0039 commented Feb 27, 2019 • edited Loading

r0039 commented Feb 28, 2019

bezarsnba commented Feb 28, 2019

bezarsnba commented Feb 28, 2019

r0039 commented Mar 1, 2019 • edited Loading

r0039 commented Mar 1, 2019

r0039 commented Mar 4, 2019

bezarsnba commented Mar 5, 2019

r0039 commented Mar 5, 2019 • edited Loading

r0039 commented Mar 5, 2019

bezarsnba commented Mar 5, 2019 • edited Loading

bezarsnba commented Mar 5, 2019

r0039 commented Mar 7, 2019

bezarsnba commented Mar 7, 2019 • edited Loading

r0039 commented Mar 7, 2019 • edited Loading

r0039 commented Mar 7, 2019 • edited Loading

r0039 commented Mar 11, 2019

r0039 commented Mar 14, 2019

r0039 commented Mar 19, 2019

yoder731 commented Feb 17, 2020

EmPRio93 commented Feb 18, 2020

yoder731 commented Feb 18, 2020

michalsarna commented Sep 14, 2020

starinasid commented Mar 17, 2023 • edited Loading

r0039 commented Feb 27, 2019 •

edited

Loading

r0039 commented Mar 1, 2019 •

edited

Loading

r0039 commented Mar 5, 2019 •

edited

Loading

bezarsnba commented Mar 5, 2019 •

edited

Loading

bezarsnba commented Mar 7, 2019 •

edited

Loading

r0039 commented Mar 7, 2019 •

edited

Loading

r0039 commented Mar 7, 2019 •

edited

Loading

starinasid commented Mar 17, 2023 •

edited

Loading