❓FAQ

Why can't I find some entities in the Discovery page?

After successfully adding a plugin (e.g. Github), it will immediately start pulling data and creating suggestions for you to accept or ignore in the Discovery page.

However, there a few situations where you may not find entities you were expecting to find:

• The entities were excluded from the data collection in your plugin:

  • When setting up your plugin, you have the ability to include or not specific resource types.

  • When resources are disabled at this stage, plugins will not generate associated entities from them and as result all downstream operations are not happening either (Suggestions are not added to your Discovery menu, Entities are not added to your Software Catalog, etc.)

  • How to remedy?

    • You can recreate your plugin with different settings.

• The entities were ignored during data collection:

  • To prevent pulling outdated or stale data from your data sources and flooding your catalog with unactionable entities, our plugins are set by default with policies to reduce noise.

    For instance in the case of Git providers:

    • Repositories with no activity over the last 3 months are ignored

    • Repositories that have been archived are also ignored

    • All entities related to ignored repositories (Pull Requests, Issues, Deployments, etc.) are consequently ignored

  • How to Remedy?

    • You can opt to run your plugins as Self Hosted with Galaxy, our Self Hosted Integration Framework and update the policies as you see fit.

• Your Automation Rules do not include the logic for creating expect Suggestions:

  • Each of your data sources (Github, GitBucket, Pager Duty, Datadog, etc.) uses their own language and definition for their resources (e.g. MRs for Gitlab and PRs for Github, both Datadog and Pager Duty have a definition of what makes a "Service", etc.).

  • To reconcile these differences, a common data model is created in your Org and these data-source-specific resources are converted to entities fitting it. This conversion is handled by Automation Rules.

  • While many rules are provided out of the box, you have the ability to create, update or delete them to better fit your needs (since the data model is also editable).

  • How to remedy?

    • You can update your Automation Rules definitions to make sure they include the entities you were missing

• The missing entities have actually already been added to the catalog:

  • When suggestions are created then accepted, their underlying entities are no longer generating Suggestions in order to prevent constant noise.

  • As a result you will not find them in your Discovery menu since they have already been imported into your active Software Catalog.