dentials for authentication to the Comet platform:api_key: Mandatory API key token of your Comet account.

project_name: The name of the project where you're sending the new experiment. If the project is not specified, the experiment is put in the default project associated with your API key.

workspace: Optional. The name of the workspace where your project is located. If not specified, the default workspace associated with your API key will be used.

This option configures the credentials for the Comet platform 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 Comet experiment tracker

zenml experiment-tracker register comet_experiment_tracker --flavor=comet \

--workspace=<workspace> --project_name=<project_name> --api_key=<key>

# Register and set a stack with the new experiment tracker

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

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

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

zenml secret create comet_secret \

--workspace=<WORKSPACE> \

--project_name=<PROJECT_NAME> \

--api_key=<API_KEY>

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

# Reference the workspace, project, and api-key in our experiment tracker component

zenml experiment-tracker register comet_tracker \

--flavor=comet \

--workspace={{comet_secret.workspace}} \

--project_name={{comet_secret.project_name}} \

--api_key={{comet_secret.api_key}}

...

Read more about ZenML Secrets in the ZenML documentation.

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

How do you use it?