Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

This node operation retrieves multiple events related to a specific customer from the Druva MSP platform. It is designed to fetch detailed event logs filtered by various criteria such as date ranges, categories, event types, features, severity levels, and initiators. This functionality is useful for monitoring customer activity, auditing changes, tracking alerts, and analyzing event trends within a customer's environment.

Practical examples include:

  • Fetching all login-related events for a customer within the last 30 days.
  • Retrieving audit trail events filtered by specific event types or categories.
  • Monitoring critical alerts or warnings generated for a customer in the current month.
  • Generating reports on customer-related activities filtered by feature or severity.

Properties

Name Meaning
Customer ID The unique identifier of the customer whose events are to be retrieved.
Return All Whether to return all matching results or limit the output to a specified number.
Limit Maximum number of event results to return when "Return All" is false.
Date Selection Method Choose how to filter events by date:
- All Dates (no date filtering)
- Specific Dates (filter between start and end dates inclusive)
- Relative Date Range (predefined relative periods like current month, last 30 days, etc.)
Start Date Start date for filtering events (inclusive). Used only if "Specific Dates" is selected.
End Date End date for filtering events (inclusive). Used only if "Specific Dates" is selected.
Date Range Predefined relative date range for filtering events, e.g., Current Month, Previous Year, Last 90 Days, Year To Date. Used only if "Relative Date Range" is selected.
Filter by Category Whether to filter events by their category.
Category Categories of events to include when filtering by category. Options: Event, Audit, Alert.
Filter by Event Type Whether to filter events by specific event types.
Event Type Specific event types to include when filtering by event type. Includes many predefined types such as Admin Login Success, Client Created, Customer Updated, Tenant Suspended, Commercial License Expired MSP, etc.
Filter by Feature Whether to filter events by the feature/component they relate to.
Feature Features/components to filter by. Options include Admin, Client, Customer, Customer Contact, Service Plan, Settings, Tenant, MSP.
Filter by Severity Whether to filter events by severity level.
Severity Severity levels to filter by. Options range from Emergency (0) to Debug (7), covering standard syslog severity levels.
Filter by Initiator Whether to filter events by who initiated them (applies to Audit category events).
Initiated By Text filter applied to initiator name or ID fields in event details.
Options Additional options:
- Include Details: Whether to include full event details in the output (default true).
- Format Timestamps: Whether to convert timestamps to human-readable format (default true).

Output

The node outputs an array of event objects in the json field. Each event object contains details about a single event matching the specified filters. The structure typically includes:

  • Event metadata such as event ID, timestamp, category, type, severity, and feature.
  • Customer and tenant identifiers.
  • Initiator information if applicable.
  • Detailed event data if "Include Details" is enabled.
  • Timestamps formatted as readable strings if "Format Timestamps" is enabled.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Druva MSP API with appropriate API authentication credentials configured in n8n.
  • The node uses the Druva MSP API base URL https://apis.druva.com.
  • Pagination handling is implemented internally to support fetching all items if requested.
  • No additional external services beyond the Druva MSP API are required.

Troubleshooting

  • Common Issues:

    • Invalid or missing Customer ID will cause the API request to fail or return no results.
    • Incorrect date filters (e.g., start date after end date) may result in empty responses.
    • Filtering by event types, categories, or features that do not exist for the customer will yield no events.
    • API rate limits or connectivity issues can cause errors during data retrieval.

  • Error Messages:

    • Errors returned from the Druva MSP API will be surfaced with their message text.
    • If the node encounters an unimplemented resource or operation, it throws an error indicating the unsupported resource.
    • Network or authentication failures will produce corresponding error messages; ensure API credentials are valid and network access is available.

  • Resolution Tips:

    • Verify the Customer ID is correct and accessible with your API credentials.
    • Double-check date filters and ensure logical date ranges.
    • Use smaller limits or enable pagination to avoid large data requests.
    • Confirm API credentials and permissions are properly set up in n8n.

Links and References

Discussion