Agenda

  • Logging Frankfurt Scope
  • Draft Frankfurt spec ONAP Application Logging Specification v1.3 (Frankfurt)
    • What is the difference between the rows that are in green vs yellow? Green represents required field where as yellow represents optional field.  (tick) Prudence to add a legend to the table 
    • Can we remove the following columns in the spec? It was agreed to remove the following columns from the table.
      • Applicable (per log file)
      • Marker Associations
      • Moved MDC to standard attribute
      • Removed (was in the older spec)
      • Derived
      • Historical
      • Acumos ref
      • Use Cases
    • Would like to add a new column named Notes to note the changes from the Casablanca spec Agreed by all
    • Do we need to update RequestID to TransactionID as per LOG-232 (discussed back in 20180426)? Keep it as "RequestID" and close LOG-232
    • Dave Williamson , was the discussion on August 6 - 14, 2018 regarding "Message", "Thread ID" and "Logger Name/class name" completed? See Dave's comment below and this is considered complete.
    • Dave Williamson Is the description of InstanceID already updated with the discussion on August 7, 2018? Action: Prudence to update the description
      Updated to:
      An unique ID to differentiate between multiple instances of the same (named) log writing service/application.  For example, either the Kubernetes pod ID or UUID can be used for this field.
    • Is there any components still write log to /var/log/ONAP_EELF?
    • ---------------------------------------------------------
      The following items will be moved to the next meeting:
    • We owe Steve Smokowski an answer for his question on August 30, 2018 (Response Code and Response Description) and September 4, 2018 (Invoke and Invoke-return).
    • What is needed for Michael's TODO on November 21, 2018 regarding X-FromAppId?
    • Still need to address the issue with 2 test environments and only 1 log instance?  Dave Williamson reported it on December 6, 2018
    • The description for p_message should be updated to "standard attribute - defined in logback.xml - Message - used for %msg%" as suggested by Lorraine Welch on  July 3, 2019?
    • Removing "VirtualServerName" as mentioned by Dave Williamsonon July 23, 2019?
    • Still need a description for ServiceInstanceID, any taker?
    • Any feedback on Kevin Smokowski's comment on August 6, 2019 regarding the use of User-Agent as PartnerName?
    • Any feedback on Kevin Smokowski's comment on August 5, 2019 regarding the value of ServerIPAddress in the case of docker & kubernetes deployment?
    • Any updates needed for TargetEntity and PartnerName?  Mentioned on August 15, 2019 (a conversation between Dave and Kevin)
    • Any feedback on composite RequestID or NOT composite RequestID (from October 2, 2019)?

Attendees

Notes

  • Next meeting October 22, 2019
  • No labels

1 Comment

  1. Dave Williamson

    Regarding this item:  discussion on August 6 - 14, 2018 regarding "Message", "Thread ID" and "Logger Name/class name" completed? Dave to confirm

    • Log Detailed Message – This was added (see p_message)
    • Thread ID and Logger Name/class name – These were not added to the table because the logger should be providing them (as opposed to the application needing to set them); however, he did add some descriptions that cover these items

    I think we can consider this closed.