AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node operation, "Retrieve List Logs" under the "List" resource, is designed to fetch log entries related to lists from an external service. It allows users to specify various filters such as date range, severity level, user, and other criteria to narrow down the logs retrieved. This functionality is useful for monitoring list activities, auditing changes, troubleshooting issues, or analyzing user interactions with lists.

Practical examples include:

  • Retrieving all error-level logs for a specific list within a given date range.
  • Filtering logs by a particular user to audit their actions on lists.
  • Extracting logs that match certain filter criteria to analyze system behavior or usage patterns.

Properties

Name Meaning
Datefilter A string value used to filter logs based on date criteria (e.g., a date range or specific date).
Filter A string representing additional filtering criteria to refine which logs are retrieved.
Listlogs A string specifying the particular list or log category to retrieve logs from.
Severity A string indicating the severity level of logs to fetch (e.g., error, warning, info).
User A string identifying the user whose actions or logs should be included in the results.

Output

The node outputs JSON data containing the retrieved list logs matching the specified filters. The structure typically includes log entries with details such as timestamps, severity levels, user information, and log messages. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication to the external AvantGuard CIPP service.
  • Needs configuration of the base URL for the API endpoint via credentials.
  • Depends on the external "@avantguardllc/n8n-openapi-node" package for building request properties and handling API communication.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials can cause authentication failures.
    • Invalid or improperly formatted filter parameters may result in empty responses or errors.
    • Network connectivity problems can prevent successful API calls.
  • Error Messages:

    • Authentication errors typically indicate invalid or missing API keys; verify credentials setup.
    • Validation errors suggest incorrect input values for filters; ensure all required fields are correctly filled.
    • Timeout or connection errors imply network issues; check internet access and API availability.

Links and References

Discussion