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
  • Searching your data in Cortex
  • Using the catalog search bar
  • Search index and operators
  • Example YAML files
  • Search AWS details
  • Using global search in Cortex

Was this helpful?

Export as PDF
  1. Workspace Settings

Using search in Cortex

Last updated 1 month ago

Was this helpful?

Searching your data in Cortex

Cortex has two options for searching across your data:

  • The

    • Click the magnifying glass in the upper right corner of a list to open the search bar.

    • This search uses Lucene for the search index. See the below.

  • The at the top of the main nav

    • The global search allows you to conduct a quick search from anywhere in Cortex, and it searches across names, descriptions, and tags.

Using the catalog search bar

When you need to find a specific entity in Cortex, use the search bar at the top of any catalog:

  1. Click the magnifying glass in the upper right corner.

  2. Enter text into the search bar.

    • You can use plain text for a basic search, or use operators to refine your search.

Search index and operators

If you search for a term that includes Lucene syntax characters, such as :, try wrapping your search term in double quotes.

Below is a chart of Cortex's search index and available operators. The search fields are listed in order of weight, with title, tag and CID carrying the most weight and repo basepath, links, and custom data carrying the least weight.

Search field
Corresponding YAML field
Explanation
Examples (based on sample YAMLs below)

Title (title: or name:)

title

Searches for the entity's name as defined in the title field.

  • search doc

  • search

  • title:"search doc"

  • name:"search doc"

Tag (tag:)

x-cortex-tag

Searches for an entity tag as defined in the x-cortex-tag field. If an entity tag has more than one term separated by a hyphen, you can search for the tag using hyphens or spaces. At least one of these (or a wildcard) must be used for results to be generated.

  • search-doc

  • search

  • tag:"search-doc"

  • tag:"search"

CID (cid:)

(depends on integration)

Searches for an ID associated with an entity. This usually comes from a third-party integration.

  • ASDF1234

  • cid:"ASDF1234"

Description (description:)

description

Searches for the supplied term(s) in an entity's description.

  • example entity

  • article search example

  • description:"article"

  • description:"using search"

Group (group:)

x-cortex-groups

Searches for entity group names.

  • docs

  • writing

  • group:"writing-project"

  • group:"docs"

Owner (owner:)

x-cortex-owners

Searches for the owner(s) of an entity. If the owner is a team, Cortex searches team names and team members' names and email addresses. If the owner is an individual, Cortex searches for the user email.

  • technical writers

  • sample.user

  • owner:"sample"

  • owner:"technical"

Member (member:)

x-cortex-team, members

Searches for the name and email address for a team member. This query only returns Team entities.

  • additional user

  • additional.user

  • member:"additional"

  • member:"user"

Slack channel (slack:)

x-cortex-slack

Searches for a Slack channel name defined in the x-cortex-slack field.

  • frontal-lobe

  • left-brain

  • slack:"frontal"

  • slack:"left"

Microsoft Teams channel (microsoft-team:)

x-cortex-microsoft-teams

Searches for a Microsoft Teams channel name defined in the x-cortex-microsoft-teams field.

  • team-docs

  • documentation

  • microsoft-team:"team-docs"

  • microsoft-team:"documentation"

Repository (repo: or repository:)

x-cortex-git, repository

Searches for a Git repository name.

  • cortex/docs

  • docs

  • repo:"docs"

  • repo:"cortex/docs"

Repo basepath (repo-basepath: or repository-basepath: )

x-cortex-git, basepath

Searches for a Git repo basepath name.

  • myEntity

  • repo-basepath:"myEntity"

Link (link:)

x-cortex-link

Searches for link based on name and URL defined under x-cortex-link.

  • docs.cortex.io

  • live docs

  • link:"live"

  • link:"docs.cortex"

Custom data (key:value)

x-cortex-custom-metadata

Searches for custom data imported from APIs, third-party integrations, and/or defined in the x-cortex-metadata block.

  • regions-of-brain:cerebrum

The key is case-sensitive.

AWS account ID (aws-account-id:)

Defined in AWS, not in an entity's YAML

Searches for the AWS account ID of an entity.

  • aws-account-id:"012345678901"

AWS account name (aws-account-name:)

Defined in AWS, not in an entity's YAML

Searches for entities with an AWS account name.

  • aws-account-name:"example-aws-account"

AWS region (aws-region:)

Defined in AWS, not in an entity's YAML

Searches for entities in an AWS region.

  • aws-region:"us-west-1"

AWS ARN (aws-arn:)

Defined in AWS, not in an entity's YAML

Searches for an Amazon Resource Name (ARN).

  • aws-arn:"arn:aws:iam::123456789012:user/johndoe"

AWS entity type (aws-type:)

Defined in AWS, not in an entity's YAML

Searches for entities of a given AWS entity type.

  • aws-type:"lambda"

AWS entity name (aws-name:)

Defined in AWS, not in an entity's YAML

Searches for an AWS entity name.

  • aws-name:"abc-lambda"

AWS primary identifier (aws-identifier:)

Defined in AWS, not in an entity's YAML

Searches for an AWS primary identifier.

  • aws-identifier: "value"

AWS secondary identifier (aws-secondary-identifier:)

Defined in AWS, not in an entity's YAML

Searches for an AWS secondary identifier.

  • aws-secondary-identifier: "value"

Example YAML files

The YAML files below show what an entity might look like based on the examples in the table above:

Search doc entity YAML

info:
  title: Search doc
  description: Example entity for an article about using search in Cortex.
  x-cortex-tag: search-doc
  x-cortex-type: service
  x-cortex-groups:
    - writing-project
    - docs
  x-cortex-git:
    github:
      repository: cortex/docs
      basepath: myEntity
  x-cortex-link:
    - url: https://docs.cortex.io/
      name: Live docs
      type: DOCUMENTATION
  x-cortex-owners:
    - name: technical-writers
      type: GROUP
      provider: CORTEX
    - type: EMAIL
      email: sample.user@fake.com
  x-cortex-oncall:
    pagerduty:
      id: ASDF1234
      type: SERVICE
  x-cortex-slack:
    channels:
      - name: frontal-lobe
        notificationsEnabled: true
      - name: left-brain
        notificationsEnabled: true
  x-cortex-microsoft-teams:
    channels:
    - name: team-docs
      teamName: documentation
      description: This is a description for the docs channel in Teams.
      notificationsEnabled: true
  x-cortex-metadata:
    regions-of-brain: cerebrum, cerebellum

Technical writers team YAML

info:
  title: Technical writers
  description: Example Team behind the article about using search in Cortex.
  x-cortex-type: team
  x-cortex-tag: technical-writers
  x-cortex-team: 
    groups:
      - name: cortex/technical-writers
        provider: GITHUB
    members:
      - name: Additional User
        email: additional.user@example.com
        notificationsEnabled: true

An entity's title, tag, and ID have carry the greatest weight in a search.

Search AWS details

Using global search in Cortex

You can search the Cortex platform from any page using the global search function. Global search pulls from names, descriptions, and tags.

Click Search in the upper left side of Cortex, and a search modal will appear:

You can search across all items, or you can click into tabs to view entities, Initiatives, catalogs, plugins, Scorecards, Workflows, or CQL reports. Click into any item in the search results to navigate to it.

The first 10 results are displayed in the modal. Click See all to view additional results.

Searches prepend and append a to your search. For example, searching for "search doc" would be translated into *search doc* under the hood.

Cortex uses Lucene for the search index, so queries must follow .

There are additional keys available to search Amazon Web Services (AWS) details in Cortex. See for more information.

wildcard
Lucene syntax
Searching AWS entities in Cortex
search bar at the top of any catalog
available operators
global search