Analyze your audit trail

Get started in analyzing your audit trail. Learn how to sort & filter your events, and get an overview of the audit trails events recorded in elproCLOUD.

Last Updated: September 08, 2021

Analyze your audit trail

The Audit Trail, which you can access via the corresponding menu item in the main menu on the left, lists all events related to your organization account. Entries are unmodifiable (read only).

• The first section allows specifying the time range that should be considered for the analysis. Either select one of the presets Last 7 Days, Previous Week, Previous Calendar Month, Previous Year, All or specify an individual time range via the input fields. Click Show to update the events listed in the second section.
• In the second section, all events for your organization account are listed that occurred in the time range specified via the first section.

Sort your Events

The events list can sorted by different columns using the small icon to the right of the column name. Clicking on the item will toggle between ascending sorting, descending sorting and default sorting (removing sorting by the corresponding column).

Filter events

• The events list can also be filtered by specific incident numbers, events, sensors or users. Use the  icon to the right of the corresponding column.
• For example, to see all events related to a specific incident number, click on the icon in the column "Incident #".
• Then specify the incident number you would like to see in the field "Search..." and click on the "Search" button.
  
• The events list will be updated accordingly and active filtering is indicated by an icon in blue.
• In order to reset a filter click the icon an choose "Reset" in the appearing dialog.

Open Event details

• In order to see detailed information on an entry listed in the events list simply click on the corresponding row in the events list. Click again to close the event details.

Audit trail events

The following entries can be listed in the audit trail.

• Organization created: The organization account was created.
• Organization confirmed: The organization account was confirmed (by clicking the confirmation link from the confirmation email sent).
• Organization changed: Modifications to the organization account were made. Changed properties are listed in the event details with old value and new value.
• User created: A new user was created.
• User confirmed: The user account was confirmed (by clicking the confirmation link from the confirmation email sent).
• User changed: Modifications to the user account were made. Changed properties are listed in the event details with old value and new value.
• Message sent: A message like an email or SMS message was successfully sent to the recipient.
• Message sending failed: A message like an email or SMS message should have been sent but sending was not successful.
• Login successful: A user logged in successfully to the web application.
• Login failed: A user connected to the organization account (identified via a correct email address) could not log in, e.g. because he had entered a wrong password.
• Logout: A user logged out from the web application.
• New email address confirmed: A user who had changed his email address (--> User changed) confirmed this email address (by clicking the confirmation link from the confirmation email sent).
• New measurement module added: A new measurement module was registered to the organization account.
• Measurement module changed: Settings for a measurement module were changed. Changed properties are listed in the event details with old value and new value.
• Measurement module deleted: A measurement module was deleted from the organization account.
• New sensor added: A new sensor was added to the organization account.
• Sensor changed: Sensor settings were changed. Changed properties are listed in the event details with old value and new value.

• Sensor replaced: A sensor has been replaced with a new sensor.

• Sensor paused: A sensor was paused.
• Sensor restarted: A paused sensor was restarted again.
• Sensor retired: A sensor was retired.
• Sensor deleted: A sensor with all corresponding data was finally deleted from the organization account.
• Sensor alarming activated: Alarming for a sensor was activated.
• Sensor alarming deactivated: Alarming for a sensor was deactivated.
• Deviation occurred: A deviation, e.g. a breach of an alarm limit, occurred.
• Deviation no longer active: A deviation is no longer active, e.g. in case of a limit alarm the value has returned to the "good zone".
• Deviation deactivated: An active deviation was deactivated, e.g. by deactivating alarming for the corresponding sensor (--> Sensor alarming deactivated).
• Deviation acknowledged: A deviation was acknowledged.
• Sensor license model changed: Sensor settings have been changed leading to an up- or downgrade of the license model, e.g. SMS notifications were enabled/disabled for the sensor.
• Sensor license charged successfully: A due license fee could be charged successfully to the credit card.
• Sensor license charge failed: A license fee was due but could not be charged successfully to the credit card.
• Sensor license expiry warning: An expiry warning was issued or a next level of sanctions was announced for licenses already expired.
• Sensor limit profile created: A new limit profile was created.
• Sensor limit profile changed: Settings for a limit profile were changed. Changed properties are listed in the event details with old value and new value.
• Sensor limit profile deleted: A limit profile was deleted.
• Sensor issue profile created: A new sensor issue profile was created.
• Sensor issue profile changed: Settings for a sensor issue profile were changed. Changed properties are listed in the event details with old value and new value.
• Sensor issue profile deleted: A sensor issue profile was deleted.
• Module issue occurred: A module issue, e.g. a low battery warning, occurred.
• Module issue no longer active: A module issue is no longer active.
• Module issue deactivated: A module issue was deactivated, e.g. by deleting the module from the organization account (--> Measurement module deleted) while there were open module issues.
• Credit card created: A new credit card was created to the organization account.
• Credit card deleted: A credit card was deleted from the organization account.
• Service started: A service, a component of the elproCLOUD web application, was (re-)started.
• Service stopped: A service, a component of the elproCLOUD web application, was stopped.
• Application error occurred: An unexpected application error occurred.
• Run Started: A new run of a LIBERO Gx data logger was started.
• Run Stopped: A run of a LIBERO Gx data logger was stopped.