> For the complete documentation index, see [llms.txt](https://docs.cortex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.io/ingesting-data-into-cortex/entities-overview/entities/discovery-audit.md).
# Discovered entities
You may have over a hundred repositories in GitHub, dozens of cloud resources across AWS, and services running in Kubernetes; eventually, you'll likely want all of them accounted for in Cortex. With that much information, it can be hard to know at a glance that everything is tracked and that new projects are being brought into your catalogs.
The discovered entities list (formerly known as the discovery audit) gives you confidence in your catalogs by surfacing every change Cortex detects across your environment. Cortex continuously compares what already exists in your catalog against what it finds in your connected integrations—your git provider, APM tools, Kubernetes clusters, cloud accounts, and other key integrations—so you always have insight into what's new or has changed.
## Viewing discovered entities
Users with the `View Entities` permission can view discovered entities.
**To access discovered entities**:
1. From the main sidebar, expand **Catalogs**, then select **All entities**.
2. Select the **Discovered entities** tab.
The tab opens to the **Discovered** view, which lists recent changes in your environment that aren't yet reflected in Cortex, such as newly created repositories and cloud resources discovered from your integrations. Events you've chosen to ignore live under the **Ignored** view instead.
Each row in the list shows:
* **Entity** - The name of the discovered entity, prefixed with an icon for the integration it came from (e.g. GitHub or AWS).
* **Event type** - The kind of change Cortex detected, such as **New repository** or **New AWS resource**.
* **Event date** - When the change was detected. Some sources don't report a timestamp, in which case this column shows N/A.
* **Actions** - The actions available for that event. The available actions depend on the event type: new resources can be imported or ignored, while resources that are no longer detected can be deleted or ignored. See [Acting on discovered entities](#acting-on-discovered-entities)
### Searching and filtering the discovered entities list
The first time you view the discovered entities list, there may be a lot to review. To narrow the scope and start with the changes that are highest priority for you, search or filter the list.
* To search, type into the search bar in the upper-right corner of the list.
* To filter, click **Filter** in the upper-right corner of the list, then choose one or more of the following fields. Select your criteria, then click **Apply**. To clear everything and start over, click **Reset filters**.
* **Integrations** - Limit the list to events from specific integrations
* **Types** - Limit the list to specific event types
### Refreshing and exporting the discovered entities list
Two actions at the top of the list help you keep it current and share it:
* **Sync** - Prompts Cortex to re-check your connected integrations for changes, refreshing the list with the latest discovered events.
* **Export CSV** - Downloads the current list as a CSV file, which is useful for reviewing discovered entities offline or sharing them with your team.
## Acting on discovered entities
`Admins` can act on discovered entities, i.e. import, ignore, and delete.
Each event offers a set of actions in the **Actions** column, depending on its type. You can import a newly discovered entity into Cortex, delete an entity that Cortex no longer detects, or ignore any event so it no longer appears in the list.
#### Importing an entity
If Cortex detects a new resource that you want to track, you can import it directly from this page:
1. Click the **import icon** in the **Actions** column of the row containing the entity. The **Import entities** page opens.
2. Cortex opens the entity creation flow, prefilled with details from the discovered source. Configure the remaining entity details. For detailed instructions on creating each type of entity, see the relevant docs page: [Services](/ingesting-data-into-cortex/entities-overview/entities/adding-entities/add-services.md), [Domains](/ingesting-data-into-cortex/entities-overview/entities/adding-entities/domains.md), [Teams](/ingesting-data-into-cortex/entities-overview/entities/adding-entities/teams.md), or [Custom entities](/ingesting-data-into-cortex/entities-overview/entities/adding-entities/entity-types.md).
3. Click **Confirm import**.
When you import a discovered entity, Cortex generates a Cortex [entity descriptor](/ingesting-data-into-cortex/entities-overview/entities/yaml.md) (the cortex.yaml file) seeded with the discovered source. For example, importing a discovered AWS Lambda function as a resource might produce a descriptor like this:
```yaml
openapi: 3.0.1
info:
title: Taylor Lambda
description: Payment retry handler discovered from AWS
x-cortex-tag: taylor-lambda
x-cortex-type: resource
x-cortex-definition:
resourceType: lambda-function
x-cortex-groups:
- payments
```
{% hint style="info" %}
The import action isn't available for every event type. Rows where direct import doesn't apply show a disabled import icon.
{% endhint %}
### Ignoring an event
If an event appears in the list but isn't relevant, for example, a test repository that doesn't need to be imported into Cortex, you can ignore it by clicking the **eye icon** in the **Actions** column of the row containing the event. The event moves to the Ignored view. Ignoring is persistent, so the event won't reappear in the **Discovered** view.
To move an event back, open the **Ignored** view and click the **eye icon** in that row. The event returns to the **Discovered** view.
### Deleting an entity that is no longer detected
When Cortex stops detecting an entity that already exists in your catalog, e.g. its cloud resource was torn down or its APM service stopped reporting, the event appears with a **not detected** type, such as `AWS resource not detected`.
**To delete the entity from the list**:
{% hint style="warning" %}
Deleting an entity is permanent. If you'd rather remove an entity from active use but keep it for historical reference, [archive it](/ingesting-data-into-cortex/entities-overview/entities/archiving-entities.md) instead of deleting it.
{% endhint %}
1. Click the **trash icon** in the **Actions** column of the row containing the entity. The **Confirm entity deletion** window opens.
2. Review the entity that will be removed (shown with its name and Cortex tag) so you don't unintentionally remove something that's still in use.
3. Click **Delete**.
For hands-off maintenance, you can also configure [auto-archival](/ingesting-data-into-cortex/entities-overview/entities/archiving-entities/auto-archive.md) to automatically archive entities when they're no longer detected in your integrations, so they never need to be cleaned up from this list manually.
## Troubleshooting and FAQ
See common frequently asked questions and troubleshooting information below.
**Why don't I see all of my services from my APM provider in the discovered entities list?**
Cortex supports discovery for a subset of integrations. If a service comes from an integration that isn't in the list below, it won't appear as a discovered entity:
* AWS
* Datadog
* ECS
* Google Cloud
* Instana
* Kubernetes
* Lightstep
* New Relic
* Version control (Azure DevOps, Bitbucket, GitHub, GitLab)
**Why is the import icon disabled for some rows?**
The import action is only available for event types that can be created directly from this page. When an event can't be imported this way, its import icon appears disabled. You can still bring the entity into Cortex through the standard [import flow](#importing-an-entity) or via [GitOps](/configure/gitops.md).
**What's the difference between ignoring and deleting an event?**
Ignoring an event simply hides it from the **Discovered** view and moves it to the **Ignored** view; it doesn't change anything in your catalog, and you can restore it at any time.
Deleting is only available for entities Cortex no longer detects, and it permanently removes the entity from your catalog. If you want to keep an entity for historical reference, [archive it](/ingesting-data-into-cortex/entities-overview/entities/archiving-entities.md) instead of deleting it.