Entity details page

The entity details page

Each entity has its own page that centralizes data related to the entity, allowing developers to reduce context switching.

While viewing entities in a catalog, or from the Catalogs > All entities page, click an entity name to open that entity's details page.

When you first open an entity, see an overview of relevant information. If there are any active incidents, you will see them at the top of the page, in addition to recent events, on-call, owners, Slack or Microsoft Teams channels, groups, repository, language, and related domains.

During an incident, the entity details page allows you to quickly find the information you need all in one place: the active incident itself, who owns the entity and who is on-call, which Slack channel to communicate in, dependencies that could be affected, and the most recent deploys.

If data is not available for a field on the entity page, it will not appear in the overview. For example, if you do not have the Slack integration configured, then the "Slack channels" field will not be displayed.

Entity details sidebar

In the left sidebar of an entity, drill further into the entity's recent deploys, events, security vulnerabilities, monitoring metrics, and more, giving you the insight you need to solve an incident quickly and efficiently.

In the sidebar, click into each category for more information:

Entity overview categories

• API explorer: Pulls from API documentation added to your entity.
• Events: A list of recent events sourced from deploys, AWS ECS, Azure DevOps, GitHub, GitLab, Kubernetes, Opsgenie, PagerDuty, Sentry, and Snyk.
• Links & docs: Documentation links you have added to the entity, along with documentation pulled from the related repository.
• On-call & incidents: On-call information from Opsgenie, PagerDuty, Splunk On-Call (formerly VictorOps), and xMatters, and incidents pulled from incident.io, PagerDuty, FireHydrant, and Rootly.
• Owners: See the teams who own the entity, the related Slack or Microsoft Teams channels, and a list of team members.

  • Learn more about how to define entity owners in Defining ownership.
• Entity YAML: View the entity YAML that defines this entity.

  • If you have GitOps editing enabled for this entity and you have the View GitOps logs permission, this page will display the source of the YAML file and a preview of the latest GitOps log.

Cortex features for this entity

• Scorecards: A list of any Scorecards that are in progress where this entity is being scored. In additional, see the average score, median score, and a graph showing the entity's scores over time.
• Initiatives: A list of all active Initiatives for this entity, including the Scorecard's current level and the due date of the Initiative.
• Workflows: A list of Workflows that include this entity. If any Workflows are pending approval and you were designated as an approver when the Workflow was created, you will see the pending approval at the top of this page. This page also includes a list of recently run Workflows and the ability to run any related Workflows.

Connections for this entity

Under the "Connections" header, integration data for the entity is contextually grouped. When you configure integrations, data will be pulled in to the following sections on the entity details page:

• CI/CD: Pulls from deploys API, Azure DevOps, Bitbucket, Buildkite, CircleCI, GitHub, and GitLab.
• Code & security: Pulls from Checkmarx, Codecov, GitHub, GitLab, Mend, Snyk, SonarQube, Veracode, and Wiz.
• Custom data & metrics: Pulls from custom data and Eng Intelligence custom metrics.
• Dashboard: Pulls from charts configured in the entity's YAML file for Datadog, Grafana, and New Relic.
• Error tracking: Pulls from BugSnag, Rollbar, and Sentry.
• Environments: Pulls from AWS and Kubernetes.
• Issue tracking: Pulls from Azure DevOps, ClickUp, GitHub, GitLab, and Jira.
• Monitoring: Pulls from Coralogix, Datadog, Dynatrace, Google Observability Cloud, Lightstep, New Relic, Prometheus, Splunk Observability Cloud (formerly SignalFX), and Sumo Logic.
• Packages: Pulls from the packages API and any packages automatically discovered from your configured git repositories.
• Repository: Pulls from Azure DevOps, Bitbucket, GitHub, and GitLab.
• Integration settings: This page lists the integrations that are enabled and connected for this entity.

Plugins for this entity

Under the "Plugins" header, see any plugins in your workspace that are relevant to this entity.

More information on entities

Learn more about entities in Manging entities.