[ZBX-20206] web.certificate.get - Unsupported item key. Created: 2021 Nov 11  Updated: 2021 Nov 20  Resolved: 2021 Nov 20

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 5.0.17
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Tiago Cruz Assignee: Antons Sincovs
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Steps to reproduce:

  1. Install zabbix_agentd 5.0.17
  2. Run "zabbix_agentd -t web.certificate.get"

Result:
**

web.certificate.get                           [m|ZBX_NOTSUPPORTED] [Unsupported item key.]

Expected:

Works as expected 

This problem has been solved with the introduction of the new WebCertificate plugin available as a part of  Zabbix agent 2 5.4.4 release (also back-ported to Zabbix 5.0.15): 

https://mailchi.mp/2fb18ca718c6/zabbix-news-all-the-latest-updates-together-4858662?e=c5cd256baa

 

 

[tiago.cruz@vinhedo2 ~]$ zabbix_agentd -t agent.version
agent.version                                 [s|5.0.17]
[tiago.cruz@vinhedo2 ~]$ zabbix_agentd -t web.certificate.get
web.certificate.get                           [m|ZBX_NOTSUPPORTED] [Unsupported item key.]


 Comments   
Comment by Antons Sincovs [ 2021 Nov 19 ]

Hello, Tiago!

From the CLI listinng included:

[tiago.cruz@vinhedo2 ~]$ zabbix_agentd -t agent.version agent.version                                 [s|5.0.17]

and the step #1:

Install zabbix_agentd 5.0.17

It is apparent that you are trying to refer to "Web certificate" specific keys using Zabbix agent (version 1). However this functionality is only incorporated in Zabbix agent 2.

Thus you need to install the Zabbix agent 2 first and then you will be able to use these "Web certificate" specific keys. For example:

zabbix_get -s <zabbix_agent_addr> -k web.certificate.get[<website_DNS_name>]
web.certificate.get[www.google.com]           [s|{"x509":{"version":3,"serial_number":"f0cffaf486aea5990a0000000110379b","signature_algorithm":"SHA256-RSA","issuer":"CN=GTS CA 1C3,O=Google Trust Services LLC,C=US","not_before":{"value":"Oct 18 10:15:56 2021 GMT","timestamp":1634552156},"not_after":{"value":"Jan 10 10:15:55 2022 GMT","timestamp":1641809755},"subject":"CN=www.google.com","public_key_algorithm":"ECDSA","alternative_names":["www.google.com"]},"result":{"value":"valid","message":"certificate verified successfully"},"sha1_fingerprint":"5e4b8fb5bf60fdbaf172079bd33a35d8d03b7557","sha256_fingerprint":"51d2c53a71836cfe5273f984b46a8d750fad355c549b8bdd0bd6fd459d4681ac"}]

Kind regards,

Antons Sincovs

 

Comment by Tiago Cruz [ 2021 Nov 19 ]

Hello @antons,

But in the email that "you" send to us (mail marketing?), says that:

 ... (also back-ported to Zabbix 5.0.15): 

https://mailchi.mp/2fb18ca718c6/zabbix-news-all-the-latest-updates-together-4858662?e=c5cd256baa

 

So this was a mistake?  

Thanks!

Comment by Antons Sincovs [ 2021 Nov 19 ]

This is not a mistake - 5.0.15 in this case refers to Zabbix environment as whole (Zabbix server, Zabbix frontend, Zabbix agent 2). In case you use 5.0 LTS you have to use the corresponding Zabbix agent 2 version >=5.0.15. Thus this new functionality can be used with Zabbix server >=v5.0.15 + Zabbix agent 2 >=v5.0.15

5.4.4 release (also back-ported to Zabbix 5.0.15): 

Means that this new functionality was first interfoduced in 5.4.4 (provide by Zabbix agent 2 5.4.4), but was so useful that was also "backported" (tranferred to an older version) to 5.0.15 (provided by Zabbix agent 2 v5.0.15 and onwards)

 

Comment by Tiago Cruz [ 2021 Nov 19 ]

Many thanks Antons,

So, I thought this was a feature from  zabbix_agentd >= 5.0.15  

You can close this issue, thanks!

Comment by Antons Sincovs [ 2021 Nov 20 ]

You are always welcome, Tiago!

Generated at Fri May 02 07:41:09 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.