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
  • Log retention
  • Accessing notification logs in Cortex
  • Access notification logs via the Cortex UI
  • Filter the notification logs list
  • View more information about a notification
  • Resend a notification
  • Access notification logs via API

Was this helpful?

Export as PDF
  1. Workspace Settings
  2. Notifications

Notification logs

Last updated 2 months ago

Was this helpful?

Notification logs allow you to understand and monitor what are being sent for your workspace, who they're sent to, and how users are engaging with them.

Log retention

Notification logs are retained for 30 days, and the contents of the notifications are retained for 14 days.

Accessing notification logs in Cortex

Access notification logs via the Cortex UI

Notification log summary

The summary at the top of this page includes:

  • A count of how many notifications are enabled

    • In the upper right corner of the Notification logs page, click Workspace notifications to visit the Notifications page where you can review the list of enabled notifications.

  • The number of notifications delivered in the last 7 days

  • The number of notifications that failed to deliver in the last 7 days

Notification log list fields

The list of notifications includes:

  • Timestamp when the notification was sent

    • The timestamp is based on the client timezone from your browser. Hover over the timestamp to view the timezone being used.

  • The name of the notification

    • An icon appears next to the notification name to indicate which medium was used to notify the user.

  • The status

    • Statuses include:

      • Completed: The message was delivered successfully.

      • Completed with errors: Some recipients received the notification, but some did not. Click the notification to review details.

      • Failed: Notification failed to be delivered.

      • Ignored: The notification was ignored. This can occur for several reasons, including:

        • Disabled workspace: This status will appear if the notification medium has been disabled for the workspace, but there was an attempt to send a notification via that medium. For example, if an email notification is triggered, but email notifications are disabled for the workspace.

        • Scorecard disabled: Notifications are disabled for a scorecard.

  • How many times it was sent

  • The object that triggered the notification (e.g., a Scorecard, entity, initiative, etc.)

  • The ability to resend the notification.

Filter the notification logs list

  1. In the upper right corner of the list, click Filter.

  2. Select and configure filters for any of the following:

    • Failed reason

    • Ignored reason

    • Notification source

    • Notification type

  3. Click Apply.

You can also sort by date:

  1. Click Date in the upper right corner.

  2. Choose whether to sort ascending or descending.

View more information about a notification

Notification logs are retained for 30 days, and the contents of the notifications are retained for 14 days.

Resend a notification

Users with the Execute notification logs permission can resend a notification to all users, or to specific users.

To resend a notification:

  1. Locate the notification in the list.

  2. A confirmation modal will appear.

  3. Click Resend notification.

Access notification logs via API

You can view notification logs in the Cortex UI or fetch them through the .

Users with the View notification logs permission can access notification logs in Cortex under .

Created: The notification has not yet been sent. If this occurs, try .

Status

Click into a log to open a side panel showing the date a notification was sent, when it was last resent, who the recipients of the message were, and the contents of the notification:

In the row for the notification, click the Resend icon on the right side.

If the previous notification did not successfully send to all recipients, you will have the option to only resend to recipients who didn't receive the notification.

Notification logs can also be accessed through the .

Settings > Notification logs
public API endpoint
Cortex API
resending the notification
notifications
See the notification list on the notification logs page
The notification log summary is at the top of the page