Fixed
Details
Assignee
UnassignedUnassignedReporter
Ubence QuevedoUbence QuevedoHB Grooming Date
Feb 28, 2023HB Backlog Status
Refined BacklogFD#
1723Original estimate
Time tracking
No time logged1d remainingAffects versions
Priority
Medium
Details
Details
Assignee
Unassigned
UnassignedReporter
Ubence Quevedo
Ubence QuevedoHB Grooming Date
Feb 28, 2023
HB Backlog Status
Refined Backlog
FD#
1723
Original estimate
Time tracking
No time logged1d remaining
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created February 24, 2023 at 10:46 PM
Updated June 15, 2023 at 6:09 PM
Resolved June 15, 2023 at 6:09 PM
For the Horizon/Meridian documentation on Replacement Tokens, specifically Parameter Tokens with the following tokens documented:
%parm[all]%
%parm[values-all]%
%parm[names-all]%
%parm[<name>]%
%parm[##]%
%parm[#<num>]%
%parm[name-#<num>]%
However, there seems to be a hidden bit of functionality that isn’t documented, but is referenced in alec code with the following parameter token:
%parm[name-#1<num>.-<num>]%
The above will extract the digit from the specified position [right to left] of specified parameter name.
For example:
%parm[name-#1.-4]%
would extract the 4th position [right to left] of the 1st parameter name. When applied to .1.3.6.1.2.1.15.3.1.14.10.224.10.18, it would grab .1.3.6.1.2.1.15.3.1.14.10.224.10.18
That alec code example for grabbing bits of a parameter value does work in Horizon/Meridian, and helped with trying to pull an IP address from an event, but again, it isn't documented.
The question is, is this the only option for this parameter token that isn’t documented? If there are others, I’d like to get this as well as any others into the documentation.