Using the Discovery audit

You may have over a hundred repositories in GitHub, and eventually, you will likely import all of them into Cortex. This much information can make it difficult to know at a glance that all repositories are accounted for and all new projects are being imported into and tracked within Cortex.

The Discovery audit guarantees confidence in your catalogs by listing all changes that Cortex has detected. Cortex compares everything that exists within the system to what it discovers within your Git tool, APM tool, Kubernetes cluster, and other crucial integrations so you have insight into all of the changes happening across all of your environments.

You can find the Discovery audit under Tools in the main nav.

On the Discovered page, you’ll see a full list of detected changes so you can easily see what updates need to be made.

The first few times you use the Discovery audit, there may be a lot to review. To make things easier, you can search or filter the list by integration to focus on the highest priority changes.

Importing and removing entities

Cortex will tag detected changes to signify whether an entity or repository has been discovered, archived, or deleted.

If Cortex detects a new service or resource, you can import it directly from this page. Select the + icon to go directly to the entity import flow.

If Cortex no longer detects a given entity, you also have the ability to delete that entity or repository directly from this page by selecting the trash can icon. This will open a modal window with the entities that will be impacted.

This window gives you the opportunity to review all potentially impacted services before deleting, so you don’t unintentionally remove something from Cortex.

Ignoring events

If an event appears within the Discovery audit, but is irrelevant — for example, a test project that doesn’t need to be imported into Cortex — you can ignore it by clicking the closed eye icon.

The ignore action is persistent, so the event won’t appear again within the discovery audit. Although ignoring is persistent, it’s not permanent — you can view ignored events and unignore them at any time on the Ignored page. Select the open eye icon next to an event on the Ignored page to return it to the Discovered list.

At first, there may be a lot of discoveries to sort through, so you may find yourself ignoring quite a few events. As time goes on and as your team maintains the catalogs, there will be fewer changes that appear within the discovery audit, so you’ll want to pay attention to those that do.