Please enable JavaScript to view this site.

QPR Knowledge Base 2023.1

  •      
  • Navigation: Administrator's Guide > Appendices > Appendix F: Audit Logs and User Audit Logs > Audit Logs

    Audit Log for QPR Metrics

    Scroll Prev Top Next More

    All operations targeted at a QPR Metrics model can be recorded into a log file called "MetricsServerAudit.txt" located in the "Audit" folder under the log folder that can be defined in the Server log settings of the Common section in the QPR Configuration Manager utility. To enable logging, launch QPR Configuration Manager, select Server log settings from the Common section, and select Logging enabled from the Audit log settings for QPR Metrics Server.

     

    The Structure of the Log File

     

    When the audit trail writing is enabled, a session entry will be written into the log file. In each entry there is a header, event, and footer section.

     

    Header Section

     

    The header section starts the session, and it will be written into the log file when the QPR Metrics Server is started. Header contains a time stamp, such as the following:

     

    ### Audit Trail logging started at 4.3.2003 17:44:55 ###

     

    Event Section

     

    When an operation (action) is committed to the QPR Metrics Server (or a Database Management System), a corresponding event will be written into the log file to the event section. The following actions are recorded:

     

    manual input of a new value

    manual change of a value

    manual delete of a value

    value inputted by a scheduled SQL import

    value inputted by a SQL mass import

    value changed by a scheduled SQL import

    value changed by a SQL mass import

    element is created

    element is deleted

    model is created

    model is deleted

    model is imported

    model is exported

    model is replaced

    model is opened

     

    note

    Note


     

    Calculated values are not recorded.

     

    An entry (a record) in the event section contains the following data (fields) on action:

     

    When the action was made?

    date: <mm>/<dd>/<yy>

    time: <hh>:<mm>:<ss>

     

    Who made the action?

    login name: <user's login name>

    user name: <user's real name>

     

    What was the target?

    name of the model: <model name>

    scorecard identifier: <scorecard identifier>

    name of the scorecard: <scorecard name>

    element identifier: <element identifier>

    name of the element: <element name>

    series identifier: <series identifier>

    name of the series: <series name>

    name of the period: <period name>

     

    What kind of an action was made?

    type of an action: User | System <import name>

    action: Value Change | Value Deletion | Create Element | Delete Element

     

    Value after and before the action.

    previous value, formatted according to value's unit: <null> | <value>

    current value, formatted according to value's unit: <null> | <value>

    value's unit: <unit>

     

    Record's end mark is a line feed (LF+CR) and fields are separated with tabulators.

     

    Footer Section

     

    The footer section ends the session, and it will be written into the log file when the QPR Metrics Server is shut down.  Footer contains a time stamp, such as the following:

     

    ### Audit Trail logging stopped at 5.3.2003 17:44:55 ###

     

     

    warning

    Warning


     

    Audit log file can become very large.