Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

The "Get Many MSP Events" operation in the Druva MSP node retrieves multiple Managed Service Provider (MSP) events from the Druva MSP API. This operation is useful for monitoring, auditing, and analyzing various MSP-related activities such as logins, administrative changes, alerts, and license status updates. It supports filtering by date ranges, event categories, event types, features, severity levels, and initiators, allowing users to tailor the event data they retrieve.

Practical examples include:

  • Fetching all MSP events within the last 30 days to audit recent administrative actions.
  • Retrieving only critical or alert-level events related to licenses expiring soon.
  • Filtering events initiated by a specific user to investigate security incidents.

Properties

Name Meaning
Return All Whether to return all matching results or limit the number of returned events.
Limit Maximum number of events to return when "Return All" is false. Minimum value is 1.
Date Selection Method Choose how to filter events by date:
- All Dates (no date filter)
- Specific Dates (filter between start and end dates inclusive)
- Relative Date Range (predefined ranges 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 The categories of events to return. Options are: Event, Audit, Alert. Can select multiple.
Filter by Event Type Whether to filter events by specific event types.
Event Type Specific event types to return. Includes many detailed options such as Admin Login Success, Client Created, Tenant Suspended, Commercial License Expired MSP, etc. Multiple selections allowed.
Filter by Feature Whether to filter events by feature/component.
Feature Features/components related to events. Options include Admin, Client, Customer, Customer Contact, Service Plan, Settings, Tenant, MSP. Multiple selections allowed.
Filter by Severity Whether to filter events by severity level.
Severity Syslog severity levels to filter by. Options: Emergency (0), Alert (1), Critical (2), Error (3), Warning (4), Notice (5), Informational (6), Debug (7). Multiple selections allowed.
Filter by Initiator Whether to filter events by who initiated them (applies to Audit category events).
Initiated By Text filter applied to initiatorName and initiatorId fields in event details to find events initiated by a specific user or entity.
Options Additional options collection:
- 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 under the json field. Each event object contains details about an MSP event, including but not limited to:

  • Event identifiers and timestamps.
  • Event category (e.g., Event, Audit, Alert).
  • Event type (e.g., Admin Login Success, Tenant Suspended).
  • Related feature/component (e.g., Admin, Tenant).
  • Severity level.
  • Initiator information (if applicable).
  • Detailed event metadata depending on the "Include Details" option.
  • Timestamps formatted as readable strings if "Format Timestamps" is enabled.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Druva MSP API via an API key credential configured in n8n.
  • The node uses the base URL https://apis.druva.com.
  • Proper permissions on the API key are necessary to access MSP event data.
  • No additional external dependencies beyond the Druva MSP API.

Troubleshooting

  • Common Issues:

    • API authentication failures due to invalid or expired API keys.
    • Permission errors if the API key lacks rights to read MSP events.
    • Empty results if filters are too restrictive or no events exist in the specified date range.
    • Errors parsing date inputs or invalid date ranges.

  • Error Messages:

    • Authentication errors typically indicate issues with the API key; verify credentials.
    • "Resource not implemented" error if the resource parameter is incorrect or unsupported.
    • Network or timeout errors may occur if the Druva MSP API is unreachable; check network connectivity.
    • Validation errors if required parameters are missing or invalid (e.g., limit less than 1).

  • Resolutions:

    • Ensure API credentials are correctly set up and have appropriate permissions.
    • Adjust filters to broaden the search if no events are returned.
    • Verify date formats and logical correctness of date ranges.
    • Check n8n logs for detailed error messages and stack traces.

Links and References

Discussion