You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been testing out the 'jq-json-logfilter' with REST API reading, and I do have this log filter mostly working, but I can't for the life of me figure out how the 'Prefix' is used.
I've set different values for the Prefix, but it seems to be completely ignored by RunDeck --- all data defaults back to ${data.} that is getting parsed.
For example, if I create a 'Prefix' to the value of 'tenant', does this gets prefixed at the attribute level, such as:
${data.tenant.}
or does this affect the actual exported object:
${tenant.}
Any help or some additional details around how Prefix is used by the Log Filter would be very much appreciated, but as of right now -- RunDeck seems to ignore anything I write into the prefix attribute.
Thanks a bunch! Definitely useful and needed functionality!
The text was updated successfully, but these errors were encountered:
I've been testing out the 'jq-json-logfilter' with REST API reading, and I do have this log filter mostly working, but I can't for the life of me figure out how the 'Prefix' is used.
I've set different values for the Prefix, but it seems to be completely ignored by RunDeck --- all data defaults back to ${data.} that is getting parsed.
For example, if I create a 'Prefix' to the value of 'tenant', does this gets prefixed at the attribute level, such as:
${data.tenant.}
or does this affect the actual exported object:
${tenant.}
Any help or some additional details around how Prefix is used by the Log Filter would be very much appreciated, but as of right now -- RunDeck seems to ignore anything I write into the prefix attribute.
Thanks a bunch! Definitely useful and needed functionality!
The text was updated successfully, but these errors were encountered: