Menu

#1397 logsv: Log filtering does not work correctly

never
invalid
None
enhancement
log
-
minor
2015-08-25
2015-06-29
No

When setting saLogStreamSeverityFilter attribute to other value (other than 127),
the logsv will discard all even the log record is matched with the filter.

Discussion

  • Vu Minh Nguyen

    Vu Minh Nguyen - 2015-07-03
    • status: unassigned --> assigned
    • assigned_to: Vu Minh Nguyen
     
  • Vu Minh Nguyen

    Vu Minh Nguyen - 2015-07-03
    • status: assigned --> accepted
     
  • Anders Bjornerstedt

    • Type: defect --> enhancement
     
  • Vu Minh Nguyen

    Vu Minh Nguyen - 2015-08-07
    • status: accepted --> invalid
     
  • Vu Minh Nguyen

    Vu Minh Nguyen - 2015-08-07

    I was wrong when interpreting the code line for log filter.

    Actually, in log AIS (A.02.01 - 3.4.2.2), there are 2 terms about filter.
    1. Severity value – SaLogSeverityT
    - Has value in range [0 – 6]
    - Is used when writing log record
    2. Severity bitmap – SaLogSeverityFlagsT
    - Has value in range [1 – 127], seven bits [0 -7].
    - Logsv will allow writing log whenever bit position [0 – 6] which represents ‘severity value’ is set.
    E.g: Severity bitmap = 5 (0’b101), logsv only allow emergency and critical log record.
    - saLogStreamSeverityFilter attribute shows severity bitmap. (not Severity value)

     
  • Anders Widell

    Anders Widell - 2015-08-25
    • Milestone: 5.0 --> never
     

Log in to post a comment.