Utilizing JSONPath to setup an LLD Macros

[high-t]

Hi.

Zabbix Version: 5.2.4.

I'm querying AWS CLI to discover items.
My item is as follows:

system.run["aws autoscaling describe-tags --region {$ZABBIX_ASG_REGION} --query 'Tags[?ResourceType==`auto-scaling-group` && Key==`{$ZABBIX_ASG_TAG}` && Value==`{$ZABBIX_ASG_VALUE}`]'.ResourceId --output json"]

with a JSONPath of

$.[*]

And it works. This is the reply I'm getting

[
"name1-asg",
"name2-asg"
]

But when I set a Discovery Rule with the same key, same preprocessing,



and the following LLD Macro settings:



I'm getting nothing, and no Item Prototype is resolved to an item.

What am I doing wrong?

[high-t]

vso Highly appreciate if you can you kindly shed some light on this issue.
Thank you!

[vso]

Hi, maybe this can help:

https://www.zabbix.com/forum/zabbix-help/390684-lld-with-an-item-that-is-a-list-object

The problem is that LLD Processed each array separately, for example first takes:
"name1-asg"

But unfortunately currently JSONPath implementation does not allow selecting such value, could create feature request for that.

[high-t]

Hi, maybe this can help:

https://www.zabbix.com/forum/zabbix-help/390684-lld-with-an-item-that-is-a-list-object

The problem is that LLD Processed each array separately, for example first takes:
"name1-asg"

But unfortunately currently JSONPath implementation does not allow selecting such value, could create feature request for that.

OK, Great input!
So, If I understand your reply correctly, would you say the the solution is either to construct the JSON as such that each item will be located in its own array, or alternatively, include the LLD Macro name in the JSON?

[vso]

JSON need to be in following format if possible:

[
{ "name":"name1-asg"},
{ "name":"name2-asg" }
]

Then LLD worker will iterate over array, for first entry it will take:

{ "name":"name1-asg"}

And JSONPath $.name can be used with it, unfortunately currently not possible to work with just "name1-asg" but this could be implemented in future

[high-t]

JSON need to be in following format if possible:

[
{ "name":"name1-asg"},
{ "name":"name2-asg" }
]

Then LLD worker will iterate over array, for first entry it will take:

{ "name":"name1-asg"}

And JSONPath $.name can be used with it, unfortunately currently not possible to work with just "name1-asg" but this could be implemented in future

So just to make sure I understood you correctly: With your example json will zabbix create the items per each "name" value?

[vso]

So just to make sure I understood you correctly: With your example json will zabbix create the items per each "name" value?

Yes, it will create item for each entry of array

[high-t]

Yes, it will create item for each entry of array

Well, in this case I think I'll preprocess the data coming from the API call, using JavaScript to form a JSON document out of the returning data.
Thank you very much for your help. As always, your input is pin point clear. Highly appreciated!

[high-t]

So, just to wrap things up, here is the now-working solution:

I've amended the preprocessing of this discovery rule to the following:



with the JavaScript being the following:

//Convert array into a discovery-ready JSON object
var array = JSON.parse(value)
var len = array.length;
var x = 0
output = "{ \"data\" :["
for (; x < len - 1; x++){
output += "{\"asgname\": \"" + array[x] + "\"},"
}
output += "{\"asgname\": \"" + array[x] + "\"}"
output += "]}"
return output

which gives me the following result:
[
{"asgname": "name1"},
{"asgname": "name2"}
]

I then set the LLD Macro:



Following the above, I'm now able to create a prototype objects.

Once again: Thank you vso for your help here!

[ballisticxlr]

Apologies for resurrecting such an old post but this dealing with JSON stuff is all a bit new for me. It appears like the message here is, yes JSON works but only if there is no serialzation.

So assuming that I begin with (pardon the goofy indenting, the forum doesn't seem to handle copy/paste of JSON cleanly)

{
"firstName": "John",
"lastName": "Smith",
"isAlive": true,
"age": 27,
"address": {
"streetAddress": "21 2nd Street",
"city": "New York",
"state": "NY",
"postalCode": "10021-3100"
},
     "phoneNumbers": [
     {
     "type": "home",
     "number": "212 555-1234"
     },
     {
     "type": "office",
     "number": "646 555-4567"
     }
],
"children": [
"Catherine",
"Thomas",
"Trevor"
],
"spouse": null
}​

I would need to do something more like the following, essentially stripping the input JSON down to a json formatted list of key:value pairsbut one which does not include items of the type category:key:value:

[
{"firstName": "John"},
{"lastName": "Smith"},
{"isAlive": true},
{"age": 27},
{"address": "21 2nd Street"},
{"city": "New York"},
{"state": "NY"},
{"postalCode": "10021-3100"},
{"Home number": "212 555-1234"},
{"Office number": "646 555-4567"},
{"Child 1":"Catherine"},
{"Child 1":"Thomas"},
{"Child 1":"Trevor"},
{"spouse": null}
]

I'm working with data that must for tedious reasons come out with more than a single level of nesting, so far it looks like 4 levels to begin with:

/subscriptions/subscriptionID/resourceGroups/resourceGroupName/providers/provider_name/item_name/item_value

I assume that this means that for each context, which would be:

/subscriptions/subscriptionID/resourceGroups/resourceGroupName/providers/provider_name

So in the end, I could create LLDP rules for each of the possible contexts by setting the JSON path to something like the following in the preprocessing rules:

JSONPath = $.subscriptions.subscriptionID.resourceGroups.resourceGroupName.providers.provider_name

LMK how badly I've misunderstood if I have indeed misunderstood.