LogoLogo
Login to CortexBook a DemoCortex Academycortex.io
  • Cortex Docs
  • Cortex Quick Start
  • Ingesting data into Cortex
    • Managing Entities
      • Adding entities
        • Add services
        • Add domains
        • Add teams
        • Add custom entity types
        • Defining dependencies
      • Entity details page
      • Defining ownership
      • Defining relationship types
      • Grouping entities
      • Adding external documentation
      • Adding Deploy data
      • Adding custom data
      • Viewing discovered entities
      • Archiving entities
      • Relationship graph
      • Using On-call Assistant for incidents
      • Managing Terraform infra in Cortex
    • Managing Catalogs
    • Integrations
      • Internally hosted integrations
      • ArgoCD
      • AWS
      • Azure DevOps
      • Azure Resources
      • BambooHR
      • Bitbucket
      • BugSnag
      • Buildkite
      • Checkmarx
      • CircleCI
      • ClickUp
      • Codecov
      • Coralogix
      • Custom webhook integrations
      • Datadog
      • Dynatrace
      • Entra ID (Azure AD)
      • FireHydrant
      • GitHub
      • GitLab
      • Google
      • Grafana
      • incident.io
      • Instana
      • Jenkins
      • Jira
      • Kubernetes
      • LaunchDarkly
      • Lightstep
      • Mend
      • Microsoft Teams
      • New Relic
      • Okta
      • Opsgenie
      • PagerDuty
      • Prometheus
      • Rollbar
      • Rootly
      • Sentry
      • ServiceNow
      • Slack
      • Snyk
      • SonarQube
      • Splunk Observability Cloud (SignalFx)
      • Splunk On-Call (VictorOps)
      • Sumo Logic
      • Veracode
      • Wiz
      • Workday
      • xMatters
  • Scorecards
    • Initiatives and Action items
      • Creating issues based on Initiatives
    • Scorecard rule exemptions
    • Scorecard rule filters
    • Scorecard examples
    • Scorecards as code
  • Reports
    • Executive report
    • All Scorecards report
    • Bird's eye report
    • Progress report
    • Report card
  • Eng Intelligence
    • Custom Metrics
    • Jira Metrics
    • Metrics Explorer (Beta)
  • Cortex Query Language (CQL)
    • Using CQL reports
    • Using JQ in Cortex
  • Workflows
    • Creating a Workflow
      • Workflows as code
    • Blocks
    • Running a Workflow
    • Registering a Scaffolder template
      • Scaffolder advanced usage
    • Using a Workflow to sync in ArgoCD
    • Kicking off a Jenkins pipeline in a Workflow
    • Calling internal service endpoints in a Workflow
  • Plugins
    • Creating a plugin
      • Creating a plugin proxy
    • Migrating Backstage plugins to Cortex
  • Engineering homepage
  • Workspace Settings
    • Using GitOps for Cortex
      • GitOps logs
    • Managing users
      • Roles and permissions
        • Custom roles
        • Team ownership entity editing
      • Configuring SSO
        • Microsoft Entra ID
        • Google
        • Other OIDC providers
        • Okta
          • Okta SCIM
      • Configuring identity mappings
      • Onboarding management
    • API keys, secrets, and tokens
      • Secrets
      • Personal tokens
    • Audit logs
    • Entity settings
      • Data verification
      • Auto archiving entities
    • IP allowlist
    • Notifications
      • Notification logs
    • Customizing your workspace
    • Using search in Cortex
  • Cortex API
    • REST API operations
      • API Keys
      • Audit Logs
      • Catalog Entities
      • Custom Data
        • Custom Data (Advanced)
      • Custom Events
      • Custom Metrics
      • Dependencies
      • Deploys
      • Discovery Audit
      • Docs
      • Eng Intel: User Labels
      • Entity Relationship Types (Beta)
      • Entity Relationships (Beta)
      • Entity Types
      • GitOps Logs
      • Groups
      • Initiatives
      • Integrations APIs
        • Azure Active Directory (Entra ID) API
        • Azure Resources API
        • AWS API
        • Azure DevOps API
        • CircleCI API
        • Coralogix API
        • Datadog API
        • GitHub API
        • GitLab API
        • incident.io API
        • LaunchDarkly API
        • New Relic API
        • PagerDuty API
        • Prometheus API
        • SonarQube API
      • IP Allowlist
      • Notification Logs
      • On call
      • Packages
      • Plugins
      • Queries
      • SCIM
      • Scorecards
      • Secrets
      • Team Hierarchies
      • Teams
      • Workflows
Powered by GitBook
On this page
  • Overview
  • Adding a verification period
  • Prerequisite
  • Create a verification period
  • Viewing and verifying pending verifications
  • View all verifications
  • View all entities associated with a verification
  • View your assigned verifications
  • Verify an entity
  • Deleting or editing a verification

Was this helpful?

Export as PDF
  1. Workspace Settings
  2. Entity settings

Data verification

Last updated 2 months ago

Was this helpful?

Overview

You can set data verification policies in Cortex to make sure that entities in your Cortex workspace are accurate. Verifications prompt owners and responsible users to check certain information, as determined by the person who created the verification period.

Adding a verification period

Prerequisite

You must have the Configure verification periods permission.

Create a verification period

  1. In Cortex, navigate to the page.

  2. Click +Add verification period.

  3. In the side panel, fill in the fields:

    • Start date and End date: Enter the start and end dates for the verification period. The start date cannot be in the past. The end date must be at least one day after the start date.

    • Name: Enter a descriptive name for the data verification.

    • Verification instructions: Enter clear and concise instructions that will appear on the entity's details page.

    • Require reason for verification: Check this box to require the user to include a reason when they verify the entity and confirm that its data is invalid.

    • Team member roles responsible for verification: Select which Cortex users will be responsible for verifying data.

      • If you select multiple roles, any of those users can verify data.

      • If you do not select a team member role, any user who owns the entity can verify data.

    • Entities to verify: Specify which entities the verification policy applies to:

      • Selection type: Choose whether to include or exclude the entity types you specify for this verification.

      • Entity types: Specify which entity types this verification applies to.

      • Advanced options: Further refine your selection by including or excluding groups, or defining a CQL expression.

  4. Click Create verification period.

Within a few minutes of saving the verification period, it will appear in the list of verifications on the Entity verification settings page.

Viewing and verifying pending verifications

View all verifications

View all entities associated with a verification

You can view a list of all entities associated with a verification:

    • In this side panel, you can also see at a glance which entities have been verified, which user verified them, and the date of the verification.

    • Click an entity to view its entity details page.

View your assigned verifications

Any users responsible for verifying data will be notified when the period begins, and will receive weekly reminders with outstanding verifications.

In addition to receiving notifications, you can also see a list of all outstanding verifications you are responsible for in the developer homepage. If you have any entities that require verification, you will see a Pending verifications tab on the homepage.

Verify an entity

  1. Navigate to the entity you need to verify.

    • If there is more than one outstanding verification, they'll be listed sequentially by due date.

Once all data verifications have been processed, the entity will display a Verified badge.

Viewing verification statuses

Deleting or editing a verification

  • To delete a verification, click the trash icon on the right side of the list.

  • To edit a verification, click the pen icon on the right side of the list.

    • Note that the edit option is disabled for verifications that are completed or expired.

You can see the list of all verifications in the page. At a glance, see the status, time period, and progress for each verification.

While viewing the verification list in the , click a row.

A side panel will appear, displaying all entities that this verification applies to:

At the top of the entity's details page, click Verify entity.

Review the verification instructions. If the entity data is correct, click Data is correct, then click Submit. When prompted to confirm again, click Yes.

If the data is invalid and this verification requires a reason, you will need to enter a reason into the text field before you click Submit.

Entities that have been labeled as correct, incorrect, or are still pending review are listed under . If an entity was labeled as incorrect, the reason is visible there:

You can delete or edit a verification period on the .

Entity verification settings
Entity verification settings
Settings > Data verification
Entity verification settings page
Entity verification settings