Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

This node interacts with the Druva MSP API to retrieve various reports and data related to cloud cache statistics for endpoints. Specifically, the "Get Cloud Cache Statistics Report" operation under the "Report - Endpoint" resource allows users to fetch detailed statistics about cloud cache usage filtered by date ranges, customers, and cache status.

Common scenarios where this node is beneficial include:

  • Monitoring cloud cache performance and health over specific periods.
  • Filtering cache statistics by customer accounts to analyze usage patterns or troubleshoot issues.
  • Generating reports for active, inactive, warning, or error cache statuses to maintain system reliability.

Practical example:
A managed service provider wants to generate a monthly report on cloud cache activity for selected customers to identify any caches in warning or error states. They can configure this node to select the "Current Month" relative date range, filter by specific customers, and include only caches with "Warning" or "Error" statuses.

Properties

Name Meaning
Date Selection Method Choose how to filter the report by date:
• All Dates (no date filtering)
• Specific Dates (select start and end dates)
• Relative Date Range (predefined ranges like current month, last 30 days, etc.)
Start Date The start date of the report period (required if "Specific Dates" is chosen).
End Date The end date of the report period (required if "Specific Dates" is chosen).
Date Range Select a predefined relative date range for the report when "Relative Date Range" is chosen. Options include: Current Month, Previous Month, Current Quarter, Previous Quarter, Current Year, Previous Year, Last 30/60/90 Days, Last 6/12 Months, Year To Date.
Filter by Customers Boolean flag to enable filtering results by specific customer IDs.
Customer IDs List of customer IDs to include in the report (required if filtering by customers).
Filter by Cache Status Boolean flag to enable filtering results by cache status.
Cache Status Cache status values to filter by when filtering by cache status is enabled. Options: Active, Inactive, Warning, Error.
Return All Whether to return all results or limit the number of returned items.
Limit Maximum number of results to return if "Return All" is false. Minimum value is 1.

Output

The node outputs JSON data containing the cloud cache statistics report entries matching the specified filters. Each item in the output array represents a cache statistic record with fields such as timestamps, customer identifiers, cache status, and other relevant metrics.

If binary data were involved (not indicated here), it would typically represent files or attachments related to the report, but this operation focuses on JSON data output.

Dependencies

  • Requires an API key credential for authenticating with the Druva MSP API.
  • The node depends on the Druva MSP API endpoint https://apis.druva.com.
  • The node uses internal helper functions to paginate and fetch all items from the API when needed.
  • For customer ID selection, the node dynamically loads available customers via the API.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Selecting specific dates without providing both start and end dates will result in validation errors.
    • Filtering by customers requires valid customer IDs; empty or incorrect IDs may yield no results.
    • Exceeding API rate limits or network issues may cause request failures.

  • Error Messages:

    • Errors fetching customers or other options will be logged and surfaced as messages like "Error fetching customers: [message]".
    • If the resource or operation is not implemented, the node throws an error indicating the unsupported resource.
    • API response errors are propagated and can be seen in the node's error output if "Continue On Fail" is enabled.

  • Resolutions:

    • Ensure API credentials are correctly configured and have necessary permissions.
    • Provide all required parameters based on the selected date filtering method.
    • Verify customer IDs exist and are accessible by the API user.
    • Check network connectivity and API status if requests fail repeatedly.

Links and References

Discussion