Dataiku DSS icon

Dataiku DSS

Use the Dataiku DSS API

Actions364

Overview

This node integrates with the Dataiku DSS API, enabling users to perform a wide range of operations on various Dataiku DSS resources. Specifically for the Scenario resource and the Get Scenario Logs operation, it retrieves the logs content for a specific run of a scenario or one of its steps.

Common use cases include:

  • Monitoring and debugging scenario executions by fetching their logs.
  • Automating log retrieval as part of a workflow to analyze scenario runs.
  • Integrating scenario logs into external monitoring or alerting systems.

Example: You have an automated data pipeline managed by a Dataiku scenario. Using this node, you can fetch the logs of a particular scenario run to check for errors or performance metrics.

Properties

Name Meaning
Project Key The key identifier of the Dataiku project containing the scenario.
Scenario ID The unique identifier of the scenario whose logs are to be retrieved.
Run ID The identifier of the specific scenario run for which logs are requested.
Query Parameters Optional additional query parameters to filter or paginate the logs (e.g., limit, page).

Output

The output is a JSON object containing the logs content of the specified scenario run. The structure typically includes textual log data under a logs field.

If the logs are returned as plain text, they are wrapped in a JSON object like:

{
  "logs": "log content here..."
}

No binary data output is expected for this operation.

Dependencies

  • Requires an active connection to a Dataiku DSS instance.
  • Needs valid API credentials including the DSS server URL and a user API key.
  • The node expects these credentials to be configured in n8n prior to execution.

Troubleshooting

  • Missing Credentials Error: If the node throws an error about missing credentials, ensure that the Dataiku DSS API credentials are properly set up in n8n.
  • Required Parameter Errors: The node validates required parameters such as Project Key, Scenario ID, and Run ID. Missing any of these will cause an error. Double-check that all required fields are filled.
  • API Request Failures: Network issues or incorrect server URLs can cause request failures. Verify connectivity and correct server address.
  • Parsing Errors: If the response cannot be parsed as JSON, the node attempts to return raw text. Ensure the scenario logs are accessible and the API endpoint is correct.

Links and References

This summary focuses on the Scenario resource's Get Scenario Logs operation based on the provided source code and properties.

Discussion