## Integrate Anomalo

URL: https://docs.atlan.com/apps/connectors/observability/anomalo/how-tos/integrate-anomalo

> Once you have [configured the Anomalo settings](/apps/connectors/observability/anomalo/how-tos/set-up-anomalo), you can establish a connection between Atlan and Anomalo.

Once you have [configured the Anomalo settings](https://docs.atlan.com/llms/connectors/anomalo/set-up-anomalo/llms.txt), you can establish a connection between Atlan and Anomalo.

To integrate Anomalo with Atlan, review the [order of operations](https://docs.atlan.com/llms/catalog/connector-capabilities/order-workflows/llms.txt) and then complete the following steps.

## Create an API token in Atlan

Before running the workflow, create an [API token](https://docs.atlan.com/llms/platform/get-started/api-authentication/llms.txt) or configure an [OAuth client](https://docs.atlan.com/llms/platform/get-started/oauth-clients/llms.txt) in Atlan.

## Configure the integration in Atlan

### Select the source

To select Anomalo as your source, from within Atlan:

1. In your Atlan workspace, click **Connectors** in the left sidebar.
 * If you are using the **Old UI (Classic)**, click **New Workflow** in the top navigation.

2. Click **Marketplace**.

3. Search for **Anomalo Assets** and select it.

4. Click **Install**.

5. Once installation completes, click **Setup Workflow** on the same tile.

### Create connection

You only need to create a connection once to enable Atlan to receive incoming events from Anomalo. Once you have set up the connection, you neither have to rerun the workflow nor schedule it. Atlan processes the Anomalo events as and when your checks run in Anomalo to catalog your check metadata.

To configure the Anomalo connection, from within Atlan:

1. For _Connection Name_, provide a connection name that represents your source environment. For example, you might use values like `production`,`development`,`gold`, or `analytics`.

2. (Optional) To change the users who are able to manage this connection, change the users or groups listed under _Connection Admins_.

 :::warning

 If you don't specify any user or group, no one can manage the connection - not even admins.

 :::

3. For _Host Name_, enter the URL of your Anomalo instance.

4. For _API Key_, enter the [API key you copied](https://docs.atlan.com/llms/connectors/anomalo/set-up-anomalo/llms.txt) in Anomalo.

5. For _Organization_, select your Anomalo organization from the dropdown. Click the refresh icon to reload the list of available organizations.

6. (Optional) For _SSL certificate_, if your Anomalo deployment uses a self-signed certificate, paste the certificate content in PEM format.

7. Click the **Test Authentication** button to confirm connectivity to Anomalo.

8. Once authentication is successful, navigate to the bottom of the screen and click **Next**.

### Configure the connection

On the _Metadata_ page, you can override the defaults for any of these options:

- To select the warehouses you want to include in crawling, click **Include warehouses**. (This defaults to all warehouses, if none are specified.)
- To select the warehouses you want to exclude from crawling, click **Exclude warehouses**. (This defaults to no warehouses, if none are specified.)
- To check for any [permissions or other configuration issues](https://docs.atlan.com/llms/connectors/anomalo/preflight-checks-for-anomalo/llms.txt) before running the crawler, click **Preflight checks**.
- Navigate to the bottom of the screen and click **Next**.

:::info **Did you know?** 
 If an asset appears in both the include and exclude filters, the exclude filter takes precedence.

:::

## Configure the integration in Anomalo

:::warning Who can do this?
 You need your Anomalo _Deployment Admin Superuser_ to complete these steps - you may not have access yourself.

:::

As a _Deployment Admin Superuser_ in Anomalo, you need to create an _Organization Integration_ or _Deployment Integration_ linking a newly created Atlan integration to your Anomalo deployment. This configuration is required only after you have completed integrating Anomalo in Atlan.

You need the following for this configuration:

- URL of your Atlan instance
- [API token generated in Atlan](https://docs.atlan.com/llms/platform/get-started/api-authentication/llms.txt) or [OAuth client configured in Atlan](https://docs.atlan.com/llms/platform/get-started/oauth-clients/llms.txt)

To create an Atlan integration in Anomalo:

1. Log in to your Anomalo instance as a _Deployment Admin Superuser_.

2. Create an Atlan integration in the admin interface. Enter your Atlan hostname and the [API token you generated in Atlan](https://docs.atlan.com/llms/platform/get-started/api-authentication/llms.txt) or [OAuth client you configured in Atlan](https://docs.atlan.com/llms/platform/get-started/oauth-clients/llms.txt).

3. Create an _Organization Integration_ or a _Deployment Integration_ linking the new Atlan integration to your Anomalo deployment or a specific organization.

Once you have integrated Anomalo and your checks have completed running in Anomalo, Atlan starts receiving and processing events from Anomalo. You can see your Anomalo checks cataloged in Atlan! 🎉

Note that Atlan doesn't fetch any historical check metadata. As new events are received from Anomalo, Atlan processes these events and catalogs your Anomalo checks.

:::info **Did you know?** 
 You can also [view event logs](https://docs.atlan.com/llms/governance/access-control/view-event-logs/llms.txt) in Atlan to track and debug events received from Anomalo.

:::

---