📓
Loadium Wiki
  • Welcome to Loadium
  • Getting Started with Loadium
  • Quick Start
  • Common Reasons For Execution Fails
  • Create Test
    • JMeter Test
    • Locust Test
    • Script Builder
    • Gatling Test
    • WebDriver Test
    • HLS Test
    • Understanding Test Reports
  • ABOUT LOADIUM
    • Features
    • Pricing
    • VUH - Virtual User Hour
  • ACCOUNT
    • Profile & Account
    • Subscription
  • Audit Log
  • Features
    • Test Report
    • Compare Test
    • Report PDF Export
    • Private Location
  • Test Settings
    • Split CSV
    • Sandbox
    • Multi-Step
    • Geolocation
    • Customize Setup
    • Dedicated IP
    • Send Email
    • DNS Override
    • TPS
    • Network Type
    • Test Scheduling
    • Test Failure Settings
    • JMeter Settings
    • Failure Criteria
    • Flexible Thread Scheduling
    • File Output
  • CONTINUOUS INTEGRATION SUPPORT
    • Azure DevOps Pipeline
    • Jenkins Load Testing with Loadium
  • Integrations
    • Microsoft Teams Integration
    • New Relic Integration
    • AppDynamics Integration
    • TeamCity Integration
  • Jmeter Corner
    • Built-in JMeter Functions
    • How to Install JMeter Plugins
    • Record and Play Load Testing With Jmeter in 5 Steps
    • Websocket with Apache JMeter
    • JMeter Timers
    • Handling Error Messages of JMeter Tests in Loadium
    • Details of Throughput Controller in JMeter (Splitting Threads to Different Requests)
    • How to Add a Varying Number of Parameters in Apache JMeter
    • Local Network Simulation On JMeter
    • Running Load Test with FTP Server
  • Gatling Corner
    • Introduction to Gatling
    • Gatling Recorder
    • Gatling Pros&Cons
Powered by GitBook
On this page
  • Overview
  • Logged Actions
  • Use Cases
  • Retention Policy
  • Export & Filtering

Was this helpful?

Audit Log

Overview

The Audit Log records and displays a chronological sequence of authentication-related actions taken by users. It serves as a reliable source of truth for:

  • Monitoring account activity

  • Troubleshooting suspicious behavior

  • Supporting compliance audits

  • Enhancing user accountability

You can access the Audit Log from the Account > Audit Log section.

Each log entry includes:

  • Email address

  • Action

  • Category

  • IP address

  • Date

  • Time (timezone depends on your account settings)


Logged Actions

All authentication-related actions currently captured in Loadium’s Audit Log are listed below:

user register

A new user account was created

user activation

The user's account was activated

user email activation

The user re-sent the activation email

user change-password

The user changed their account password

user forgot-password

A password reset request was initiated by the user

user-update

The user updated their account details (e.g., name, email, preferences)

login

The user successfully logged into the platform

logout

The user logged out from the platform

sub-users invitation create

An admin created a new sub-user invitation

resend Invited User Mail

A sub-user invitation email was re-sent

delete Invited User

A pending invited sub-user was deleted before activation

sub-users invitation activation

A sub-user accepted their invitation and activated their account

sub-user register

A new sub-user account was registered

sub-user update

A sub-user's details or permissions were updated

sub-user-delete

A sub-user account was deleted

google login

The user logged in using Google authentication

microsoft login

The user logged in using Microsoft authentication

sub-user microsoft login

A sub-user logged in using Microsoft authentication

amazon register

Amazon login integration was initiated

amazon activation

Amazon login integration was successfully completed

amazon user info

User details were retrieved from Amazon during authentication

company delete

A company account was deleted from the platform


Use Cases

  • Security Review: Quickly identify failed login attempts or access from unusual IPs.

  • Compliance Audits: Demonstrate access control measures to meet regulatory requirements (e.g., ISO 27001).

  • Incident Response: Trace suspicious user behavior to determine potential compromise or misuse.


Retention Policy

Audit logs are stored securely and retained for 90 days. Extended retention options may be available for enterprise customers.


Export & Filtering

  • Filter Options: By date range

  • Export: Audit logs can be exported as CSV for internal reporting or compliance use

PreviousSubscriptionNextTest Report

Last updated 9 days ago

Was this helpful?