llowing credentials for authentication to Neptune:api_token: API key token of your Neptune account. You can create a free Neptune account here. If left blank, Neptune will attempt to retrieve the token from your environment variables.

project: The name of the project where you're sending the new run, in the form "workspace-name/project-name". If the project is not specified, Neptune will attempt to retrieve it from your environment variables.

This option configures the credentials for neptune.ai directly as stack component attributes.

This is not recommended for production settings as the credentials won't be stored securely and will be clearly visible in the stack configuration.

# Register the Neptune experiment tracker

zenml experiment-tracker register neptune_experiment_tracker --flavor=neptune \

--project=<project_name> --api_token=<token>

# Register and set a stack with the new experiment tracker

zenml stack register custom_stack -e neptune_experiment_tracker ... --set

This method requires you to configure a ZenML secret to store the Neptune tracking service credentials securely.

You can create the secret using the zenml secret create command:

zenml secret create neptune_secret \

--project=<PROJECT>

--api_token=<API_TOKEN>

Once the secret is created, you can use it to configure the neptune Experiment Tracker:

# Reference the project and api-token in our experiment tracker component

zenml experiment-tracker register neptune_secret \

--flavor=neptune \

--project={{neptune_secret.project}} \

--api_token={{neptune_secret.api_token}}

...

Read more about ZenML Secrets in the ZenML documentation.

For more, up-to-date information on the Neptune Experiment Tracker implementation and its configuration, you can have a look at the SDK docs .

How do you use it?