Skip to content

User Story: Audit Logs (Version 1) #14

@Bhoomiz01

Description

@Bhoomiz01

Title:

As a system administrator, I want to use an API endpoint to store audit logs in a new table within the Ops-dashboard.


Description:

In this version, an API endpoint will be developed in the Ops-dashboard to capture and store audit logs. These logs will be saved in a dedicated table within the Ops-dashboard database to ensure all relevant actions are recorded.


Acceptance Criteria:

  1. API Endpoint for Audit Logs:

    • An API endpoint is available to log system actions.
  2. Database Table:

    • A new table is created within the Ops-dashboard database for storing audit logs.
    • The table includes necessary fields like action type, timestamp, user ID, resource ID, and description.
  3. Data Integrity:

    • The API ensures all incoming log entries are correctly formatted and stored.
  4. Error Handling:

    • Proper error handling and logging mechanisms are in place for API failures.

Steps for Validation:

  1. Send requests to the API endpoint with valid log data.
  2. Verify that the logs are correctly stored in the database table.
  3. Test the API with invalid data to ensure appropriate error messages are returned.
  4. Check the database to confirm all log entries are stored accurately.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions