Once we can turn CSV into JSON, we may also use this to select specific item values from CSV.

Please, I need the posibility to filter when I'm using db.odbc.discovery

A simple example:

{
    "data": [
        {
            "{#HOST}": "host1",
            "{#PORT}": "in",
            "{#COUNT}": "5"
        },
        {
            "{#HOST}": "host2",
            "{#PORT}": "in",
            "{#COUNT}": "12"
        },
        {
            "{#HOST}": "host3",
            "{#PORT}": "in",
            "{#COUNT}": "3"
        },
        {
            "{#HOST}": "host1",
            "{#PORT}": "out",
            "{#COUNT}": "7"
        },
        {
            "{#HOST}": "host2",
            "{#PORT}": "out",
            "{#COUNT}": "6"
        },
        {
            "{#HOST}": "host3",
            "{#PORT}": "out",
            "{#COUNT}": "5"
        }
    ]
}

And filter:

$.data[?(@.{#PORT} == 'out' )].{#COUNT}

Now I'm getting the error "json path not valid: unsupported character in json path starting with".

Lack of string searching is frustrating:

I can get $.body.quota[0].quota_remaining, but I can't look for a specific ID and return it. This means if the order of the array ever changes, my JSON is getting the wrong output.

Specifically, trying to run

$.body.quota[?(@.ID=="43639"].quota_remaining

which is perfectly valid in JSONPath, but returns

Item preprocessing step #1 failed: cannot extract value from json by path "$.body.quota[?(@.ID=="43639"].quota_remaining": unsupported character in json path starting with: "[?(@.ID=="43639"].quota_remaining"

in Zabbix.

Sample JSON:

{
 "quota": [
    {
      "ID": "43639",
      "quota_remaining": "243620855268",
      "quota_timestamp": "2018-12-04 14:00:00"
    },
    {
      "ID": "12345",
      "quota_remaining": "243620123456",
      "quota_timestamp": "2018-12-04 14:00:00"
    }    
  ]
}

 

We can check if we can extend our basic JSONPath to support ?() filter expression as described here:

https://goessner.net/articles/JsonPath/index.html

It seem that the most asked Zabbix use case is to filter JSON object by the value of it's attribute:

?(@.id) - Object that has attribute id with any value 

?(@.id == 'something') - object has attribute that equals to 'something'

?(@.id > 10) - object has attribute which is > than 10

?(@.id < 10) - object has attribute which is < than 10

also to support:
?(@.id == 10)
?(@.id != 10)
?(@.id >= 10)
?(@.id <= 10)

Dear voters, would that be enough?

That's definitely the functionality I'm after

That would be an amazing addition, I desperately need this capability to take full use of dependent items.

I'm  using regex for while:

Expression:

"Other - ADR block file read".?"{#WAIT}":"([^"])

json:

{ "data":[ {"{#FILTRO}":"1","{#EVENTO}":"Other - ADR block file read","{#WAIT}":"12.57"}]}

Return: 12.57

Also waiting for this feature. Not only about LLD, but it would be great also in simple http agent use to filter out values by IDs (attribute names) not by index.

Even support for a simple .. or [*] is missing. You need this in e.g. elasticsearch monitoring, where you can query a single item but don't know its id (P5NnsStFQgmhq-rDesa3PA).

{"nodes":{"P5NnsStFQgmhq-rDesa3PA":{"timestamp":1549990321690,"name":"node-1.example.com","transport_address":"127.0.0.1:9300","host":"127.0.0.1","ip":"127.0.0.1:9300","roles":["master","data","ingest"],"attributes":{"ml.machine_memory":"3934777344","xpack.installed":"true","ml.max_open_jobs":"20","ml.enabled":"true"},"indices":{"store":{"size_in_bytes":1809484588}}}}}

If the expression ends up returning a list, Zabbix should just use the first value.

I have a similar problem

JSON Result:

{{{ "jobs": [\{ "name": "PRC_CLV", "status": "OK"},\{ "name": "Subscribers", "status": "OK"},\{ "name": "K_ElComm", "status": "OK"},\{ "name": "K_Trans", "status": "OK"},\{ "name": "AML_BI", "status": "OK"},\{ "name": "K_FavNum", "status": "OK"},\{ "name": "K_PersInfo", "status": "OK"},\{ "name": "PlayersBonuses_SAP", "status": "OK"},\{ "name": "PlayersBonuses_BI", "status": "OK"},\{ "name": "GamesTotalBetsWins_SAP", "status": "OK"},\{ "name": "GamesTotalBetsWins_BI", "status": "OK"},\{ "name": "Transactions_SAP", "status": "OK"},\{ "name": "BRANCHES_IMPORT", "status": "OK"},\{ "name": "Correspondence_BI", "status": "OK"},\{ "name": "ODSPlayerSync", "status": "OK"},\{ "name": "OperatorsDetails_BI", "status": "OK"},\{ "name": "PlayersCases_BI", "status": "OK"},\{ "name": "OperatorsAuditTransactionsChanges_BI", "status": "OK"},\{ "name": "PlayersDocuments_BI", "status": "OK"},\{ "name": "OperatorsAuditPlayersChanges_BI", "status": "OK"},\{ "name": "OperatorsAuditPPMsChanges_BI", "status": "OK"},\{ "name": "PlayersCaseActivities_BI", "status": "OK"},\{ "name": "Transactions_BI", "status": "OK"},\{ "name": "PlayersLogins_BI", "status": "OK"},\{ "name": "PlayersPaymentMethods_BI", "status": "OK"},\{ "name": "GetSportTicketComboSystemLines", "status": "OK"},\{ "name": "PlayersBets_SAP", "status": "OK"},\{ "name": "Players_BI", "status": "OK"},\{ "name": "Extranet_EVOS", "status": "OK"},\{ "name": "Extranet_AD", "status": "OK"},\{ "name": "UIStatistics", "status": "OK"},\{ "name": "Extranet_SAP", "status": "OK"},\{ "name": "PlayersBets_BI", "status": "OK"},\{ "name": "Billing_Fraud", "status": "OK"},\{ "name": "Funnel_Fraud", "status": "OK"},\{ "name": "GetDeclinedTickets", "status": "OK"},\{ "name": "GetCombinatorBets", "status": "OK"},\{ "name": "GetSportTickets", "status": "OK"},\{ "name": "GetCustomers", "status": "OK"},\{ "name": "GetSportsMarketList", "status": "OK"},\{ "name": "DWHICTTRANS_dbo_Agent", "status": "OK"},\{ "name": "DWHICTTRANS_sce_proactive", "status": "OK"},\{ "name": "DWHICTTRANS_vw_ContactsByContacts", "status": "OK"},\{ "name": "DWHICTTRANS_cls_Contacts", "status": "OK"},\{ "name": "DWHICTTRANS_cls_Actions", "status": "OK"},\{ "name": "DWHICTTRANS_dbo_eCSRStat", "status": "OK"},\{ "name": "DWHICTTRANS_dbo_iAgentPerformanceStat", "status": "OK"},\{ "name": "DWHICTTRANS_dbo_iSkillsetStat", "status": "OK"},\{ "name": "GDPR_SAZKAMOBILE", "status": "OK"},\{ "name": "PlayersBonusesBI_XXmin", "status": "OK"},\{ "name": "TransactionsBI_XXmin", "status": "OK"},\{ "name": "PlayersBetsBI_XXmin", "status": "OK"},\{ "name": "PlayersBI_XXmin", "status": "OK"}]}}}

JSON Path depend item

$.jobs[?(@.name=='FindCharacter')].status

At http://jsonpath.com/ it works like this:

$.jobs[?(@.name=='PRC_CLV')].status return ["OK"]

Any news on this one? I was hoping it would have been in 4.2, even in just an initial form. 

Sorry, not coming in 4.2. You may consider to use JavaScript preprocessing at this point.

I has tested on version 4.2.1, the problem remains,

The expression "$.directoryQuotas[?(@.type == 'dir')].name" in the LLD macros section gives an error:

Cannot process LLD macro "{#SNQUOTAID}": json path not valid: unsupported character in json path starting with: "[?(@.type=='dir')].name".

Supporting paths like "$.*~" would allow to create any number of dependent items.

Also, I'm currently using Javascript Preprocessing to work around the JSONPath limits, but I'm incurring in more JSONPath limits... seems like the current implementation doesn't support "-" inside paths.

Path:

// $.disks.VolGroup-lv_root.Size

Error:

// Cannot create item: invalid value for preprocessing step #1: json path not valid: unsupported character in json path starting with: "-lv_root.Size".

Expected:

// As it works in "JSONPath Online Evaluator"

With dot notation only alphanumeric, '_' and '.' characters can be used in field names. Bracket notation can be used for more complex names: $.disks['VolGroup-lv_root'].Size

Thanks. I'm now bracket-escaping everything that matches

key.search(/^[0-9]*$|^[A-z]*$/) < 0

I'm completely confused with "Fix Version/s: 4.0.11rc1" and that Vitaly Zhuravlev said "Sorry, not coming in 4.2.".
So Will it be in 4.0.11? I'll keep my fingers crossed.

I'm reviewing branch "feature/ZBXNEXT-4502-4.0", planned for 4.0.

Released ZBXNEXT-4502 in:

• pre-4.0.11rc1 fa62eac8d3
• pre-4.2.5rc1 8ceddc49eb
• pre-4.4.0alpha1 c9de6ac944

The detailed description of implemented features will be added to documentation later. It's close to Java implementation with some features added and some removed.Shortly:

• only comparison and regular expression operators are supported
• sum(), first() functions are added
• stddev() function is not supported

Just in case I've missed it, do we know when 4.0.11 and 4.2.5 are due for release?

~ 2 weeks

Updated documentation:

• JSONPath functionality: 4.0, 4.2, 4.4 (new page)
• Item preprocessing: 4.0, 4.2, 4.4
• What's new: 4.0.11, 4.2.5

It would be great to extend this functionality a little bit further now!  ZBXNEXT-5422