Skip to content

Resolve "Retrieve audit events via API: MVC"

Manoj M J requested to merge 121-retrieve-audit-events-via-api-mvc into master

What does this MR do?

For #121 (closed)

This change adds the Audit Event APIs GET /audit_events & GET /audit_events/:id

In order to make this work, I had to slightly refactor the existing LogFinder service (which is the service used to filter and find audit events with the given, specific params). This service was used in the admin/audit_logs UI and I have now refactored this class so that it can be used to find audit events for both the admin area and the API.

API responses:

GET /audit_events

Screenshot_2019-09-03_at_11.41.17_AM

GET /audit_events/:id

Screenshot_2019-09-03_at_11.41.31_AM

Changes in admin page due to refactoring:

The only visible change to the end user is the change in the URL params.

Before: Screenshot_2019-09-03_at_11.35.15_AM

After:

The filtering is now done via entity_type and entity_id params, thus avoiding using event_type and one among user_id, group_id, project_id param key.

Screenshot_2019-09-03_at_11.19.17_AM

Screenshots

Does this MR meet the acceptance criteria?

Conformity

Performance and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited by Manoj M J

Merge request reports