# Project settings

Project-specific settings give you control to create and manage access tokens and to enable integration with external alert providers such as Azure Monitor.

Important notes

  • Available under Chaos Platform -> Settings
  • Access maybe restricted to members of the Project Collection Administration or Project Administration groups, or a team administrator.


# Token

Running experiments requires a token that authenticates Chaos CLI to the Proofdock Cloud. A token is scoped to the DevOps project it was generated in and as a result every DevOps project requires a separate token. A generated token will expire after a certain amount of time specified by you. Since we do not store the tokens for you, make sure to keep a generated token in a safe place.

Important notes

  • A token is scoped to the project it is generated in.
  • Tokens expire after a specified amount of time.
  • Keep the generated token in a safe place. We won't store it for you.

# Revoke a token

Revoke a token

You can revoke a token that is no longer needed. Revocation will invalidate the token and prevent accessing the Proofdock Cloud with it. You may want to revoke a token due to reasons, such as project members leaving your team or compromised security.

# Update a token

Naming a token is a good way to remember it. You can name it after the reason it was generated for. However, reasons may change or typos in the name may bother you. Just click on the access token of interest and an update panel will pop up on the right. Fix the name, save it, and go ahead with your work.

# Alerts

You can enable integration with external monitoring systems such as an Azure Monitor. Alert integrations allows you to incorporate external alerts into your chaos experiment. This allows you to verify if your system can really handle a turbulent situation without affecting service quality.

# Azure Monitor

The following procedure describes how you can enable integration with the Azure Monitor:

  1. Open the Alerts tab.
  2. Turn on Integration with Azure Monitor.
  3. Provide a list of alert rule names you want to track Azure Monitor integration

    Important notes

    Learn more about the Azure alert rules here

  4. Create or update an existing action group and add to it an action of the Webhook type. Use the Azure Webhook action URI that was generated for your project (step 2), and make sure that you have enabled a Common alert schema. Your Webhook configuration in the Azure portal should look as follows: Azure Monitor integration

    Important notes

    Make sure that your alert rules use the newly created action group to send notifications.

  5. From now on the Proofdock Cloud will be notified about alert state changes for the selected alert rules.