[ZBX-18849] Failed: cannot extract value from json by path Created: 2021 Jan 07  Updated: 2021 May 19  Resolved: 2021 May 19

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 5.0.7
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: febriyant Assignee: Elina Kuzyutkina (Inactive)
Resolution: Fixed Votes: 0
Labels: zabbix-server-mysql, zabbix_server
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File macros-2.png     PNG File sample_screen-2.png     PNG File templates-2.png     Text File zabbix_server.log    

 Description   
  1. I setup new host using default template (Template DB MSSQL by ODBC and Template OS Windows By Zabbix Agent)
  2. On Graph for MSSQL still no data 
  3. i see on zabbix_server.log return this error message  
    Failed: cannot extract value from json by path "$[?(@.object_name=='SQLEXPRESS_2019:SQL Statistics' && @.counter_name=='Batch Requests/sec')].cntr_value.first()": no data matches the specified path
  2769:20210107:133416.720 error reason for "SQLSERVER:mssql.readahead_pages_sec.rate" changed: Preprocessing failed for: [{"object_name":"MSSQL$SQLEXPRESS_2019:Access Methods","counter_name":"AU cleanup batches/sec","i...
  1. this macros on the host  
    {$MSSQL.DSN} => sql1
{$MSSQL.INSTANCE} => SQLEXPRESS_2019
{$MSSQL.PASSWORD}
{$MSSQL.PORT} => 4019
{$MSSQL.USER} =>zabbix
  1. For MSSQL.INSTANCE this is wrong ? because i got from query  
    select @@servername

    the result is 

    WIN-3HQL3VMV7Q8\SQLSERVER_2017


 Comments   
Comment by Andrey Tocko (Inactive) [ 2021 Jan 11 ]

Hello!
We need u to show us gathered data, before preprocessing.

Edit Item "MSSQL: Get performance counters" in "Template DB MSSQL by ODBC". Enable History storage period ~ 7d. Then update item and wait until u see this item data in "Monitoring->Latest Data". To speed up process u can force configuration update and press "execute now" for this item.

Regards,
Andrejs

Generated at Sun Apr 06 02:14:34 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.