Status in source: current.
Names: tmnxLogFilterParamsEntry
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"tmnxLogFilterParamsEntry",
"OBJECT-TYPE",
"SYNTAX",
"TmnxLogFilterParamsEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"Information about a particular Log Filter Parameter entry. Every Log Filter can have zero or more Log Filter Parameter match entries. The Log Filter parameter entries are checked in ascending order by their index value, tmnxLogFilterParamsIndex. Upon the first successful match, the specified actions are applied as indicated by the value of tmnxLogFilterParamsAction. No further checking against remaining tmnxLogFilterParamsEntry rows is done. Therefore, entries in this table should be sequenced from most to least explicit match criterion. It is recommended that multiple parameter entries for a log filter should be created with gaps between their index values. This allows a new entry to be inserted into an existing filter policy without needing to renumber the already existing filter parameters entries. A log filter entry in the tmnxLogFilterTable with no entry in the tmnxLogFilterParamsTable to define its match criteria set will match every log event, and the default action specified by tmnxLogFilterDefaultAction will be taken. Entries are created by user. Entries are deleted by user. There is no StorageType object, entries have a presumed StorageType of nonVolatile. \"",
"INDEX",
"{",
"tmnxLogFilterId",
",",
"tmnxLogFilterParamsIndex",
"}",
"::=",
"{",
"tmnxLogFilterParamsTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"TmnxLogFilterParamsEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Information about a particular Log Filter Parameter entry. Every Log Filter can have zero or more Log Filter Parameter match entries. The Log Filter parameter entries are checked in ascending order by their index value, tmnxLogFilterParamsIndex. Upon the first successful match, the specified actions are applied as indicated by the value of tmnxLogFilterParamsAction. No further checking against remaining tmnxLogFilterParamsEntry rows is done. Therefore, entries in this table should be sequenced from most to least explicit match criterion. It is recommended that multiple parameter entries for a log filter should be created with gaps between their index values. This allows a new entry to be inserted into an existing filter policy without needing to renumber the already existing filter parameters entries. A log filter entry in the tmnxLogFilterTable with no entry in the tmnxLogFilterParamsTable to define its match criteria set will match every log event, and the default action specified by tmnxLogFilterDefaultAction will be taken. Entries are created by user. Entries are deleted by user. There is no StorageType object, entries have a presumed StorageType of nonVolatile."
],
null,
null,
[
"INDEX",
[
[
0,
"tmnxLogFilterId"
],
[
0,
"tmnxLogFilterParamsIndex"
]
]
],
null
]
}