Zum Inhalt springen
EBF Documentation

EBF product documentation

Find help using and administering EBF applications

EBF MIDA

  • Release Notes
  • 01. Getting Started
  • 02. Initial Setup
  • 03. MIDA Overview
  • 04. Apps
  • 05. Policies
  • 06. iBooks
  • 07. App lists
  • 08. Compliance Actions
  • 09. Audit Logs
  • 10. ENS Events
  • 11. MIDA Installation Guide
  • 12. MIDA Configuration Parameter
  • 13. Import & Sync Workers
  • 14. About the Event Notification Service (ENS)
  • 15. Troubleshooting
  • 16. Browser Support
  • 17. Contact
View Categories
  • Home
  • Homepage
  • EBF MIDA

09. Audit Logs

1 min read

Audit logs show the interaction between MIDA and the MI Core.

You can access the audit logs via the MIDA interface. The Permission Audit Log:findAll is required for access.

The audit logs show the following columns:

Column Description
User The login name of the user who performed this action.
Method GET: Request data from the MI Core

POST: MIDA registrations and e.g. device actions executed by MIDA and sent to MI Core. Example: Create single devices, deregister, wake up,…

PUT: Request to add an object to the MI Core.

DELETE: request to remove an object from the MI Core

PATCH: Save changes in the MIDA database, e.g. changes to users or roles.

Permission The permission that was used to perform an action.
Example: devices:register = A device was newly created in MIDA.
The „register“ permission of the „devices“ group was used.
Input More details on the action performed.
Exec status SUCCESS: Successfully handed over to MI Core

FAILED: The command/action has failed:

Could not be passed to MI Core.

Was rejected by the MI Core.
Repeat the action and check the parameters.

 

Date Time of the command execution (format: YYYY-MM-DD).

Important: Here the time of the MIDA server is used

Duration Duration for the execution of the command in milliseconds

The search field at the top can be used to search for any text occurring in the logs.

Examples

  • devices:register,
    devices:retire>>
    When searching for :register, all new device installations are displayed.
  • MIDA Username
  • Devices username
  • E-mail address
  • Devices UUID,
    This can be used to open the device directly from the following link:
    <MIDA-URL> /#/devices/<uuid>
  • A date or time in the format: YYYY-MM-DD HH:MM:SS

The audit log contains all log entries that were performed within the mandate label.

This means:

The MIDA SuperAdmin, which uses the All-Smartphones label, only sees the entries in the audit logs that were performed under the All-Smartphones label, i.e. mainly administrative actions.

A MIDA Admin who has only assigned a client label will only see the entries for his client. No other entries.

A user of the role Support, who has assigned many different labels, always sees the audit logs belonging to this currently selected client when selecting the client label.

There is no user who can see all logs of all clients (client label). If this is desired, a user must be created who is assigned all client labels and the label „All-Smartphones“ in MIDA.

The MIDA Audit Logs shows the AppName for entries with Apps since 2.6.0.

Export MIDA Logs

From MIDA 3.0.0 on it is possible to export the MIDA Logs:

You can either export all MIDA logs or export the result of a search.

The MIDA audit logs are stored in the MIDA database.

 

Was this article useful?
Still stuck? How can we help?

How can we help?

Updated on 3. Februar 2022
08. Compliance Actions10. ENS Events
Navigate through page
  • Examples
  • Export MIDA Logs
Subscribe for EBF Newsletter
©2020 EBF-EDV Beratung Föllmer GmbH, All Rights Reserved
Imprint Terms and Conditions Privacy Statement Contact
Facebook-square Twitter-square Linkedin Xing-square Instagram
EBF Status Check