Activity Log

Collects and ingests activity log events from Aikido, providing comprehensive visibility into user activities, system operations, and security events within your Aikido organization.

Sync Type: Incremental

Details

This input collects activity log events from the Aikido API, capturing critical activities including user authentication, resource modifications, and administrative actions. The input supports incremental sync with automatic pagination and state management to ensure only new events are collected on subsequent runs.

Important Note: Aikido takes up to 1 hour to reflect actions in the activity log. If you perform an action on the Aikido platform and don't immediately see it in the activity log, this is expected behavior.

Prerequisites

Before connecting Monad to Aikido, you need:

1. An active Aikido account with appropriate permissions
2. OAuth2 Client Credentials (Client ID and Client Secret) for API authentication
3. Optionally, specific repository IDs or cloud integration IDs if you want to filter results

Setup Instructions

1. Generate OAuth2 Client Credentials

1. Log in to Aikido:

   • Navigate to your Aikido Dashboard
   • Sign in with your credentials

2. Navigate to API Settings:

   • Go to Settings in your Aikido account
   • Select API or Integrations section
   • Look for OAuth2 or API credentials management

3. Create OAuth2 Client Credentials:

   • Click Create New Client or Generate Credentials
   • Provide a descriptive name for the client (e.g., "Monad Activity Log Connector")
   • Ensure the client has permissions to access activity logs

4. Copy Your Credentials:

   • Copy your Client ID
   • Copy your Client Secret and store it securely
   • Important: Never commit your Client Secret to version control or share it publicly

2. Identify Optional Filter Values (if needed)

If you want to filter activity logs to specific repositories or cloud integrations:

1. Find Repository ID (optional):

   • Navigate to your repositories in Aikido
   • Note the repository ID you want to monitor

2. Find Cloud ID (optional):

   • Navigate to your cloud integrations in Aikido
   • Note the cloud integration ID you want to monitor

Configuration

The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.

Settings

Setting	Type	Required	Description
Client ID	string	Yes	OAuth2 Client ID for Aikido API authentication
Repository ID	string	No	Optional Aikido repository ID to scope activity log results to a specific repository
Cloud ID	string	No	Optional Aikido cloud integration ID to scope activity log results to a specific cloud account
Backfill Start Time	string	No	The date to start fetching data from (ISO 8601 format, e.g., "2024-01-15T00:00:00Z"). If not specified, no past records will be fetched

Secrets

Secret	Type	Required	Description
Client Secret	string	Yes	OAuth2 Client Secret for Aikido API authentication

Troubleshooting

Common Issues

1. Authentication Failures

   • Verify the Client ID and Client Secret are correct and haven't expired
   • Ensure the OAuth2 client has permissions to access activity logs
   • Check that the Client Secret is exactly as provided by Aikido (no extra spaces or characters)
   • Regenerate credentials if you suspect they may have been compromised

2. Missing Events

   • Remember that Aikido takes up to 1 hour to reflect actions in the activity log
   • If you performed actions recently and don't see them, wait and re-run the connector
   • Verify the Client ID has sufficient permissions to view activity logs
   • Check if you've applied optional filters (Repository ID or Cloud ID) that may be limiting results

3. No Data After Filtering

   • Verify the Repository ID or Cloud ID values are correct (check in your Aikido dashboard)
   • Confirm that the specified repository or cloud integration has activity to report
   • Try removing filters to ensure the basic connection is working

4. Rate Limiting

   • The input implements automatic rate limiting (0.3 RPS)
   • If you encounter rate limit errors, check if other processes are accessing the same API credentials
   • Consider spreading out connector runs if monitoring multiple integrations

Related Articles

• Aikido API Documentation
• Aikido OAuth2 Authentication
• Aikido Activity Log API Reference
• Aikido User Documentation

Sample Record

{
  "id": "activity_1234567890",
  "timestamp": "2024-11-15T14:30:45Z",
  "user_id": "user@example.com",
  "action": "repository_created",
  "resource_type": "repository",
  "resource_id": "repo_abc123",
  "resource_name": "my-app",
  "details": {
    "description": "Created new repository for application",
    "visibility": "private"
  },
  "status": "success",
  "ip_address": "203.0.113.42",
  "user_agent": "Mozilla/5.0..."
}