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
      • 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
  • 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
  • Create an initiative
  • Step 1: Configure the Initiative's basic details
  • Step 2: Define the Initiative's goal
  • Step 3: Finish the Initiative configuration
  • Edit Initiatives
  • View Initiatives
  • View the Initiatives list
  • View individual Initiatives
  • View Initiative action items

Was this helpful?

Export as PDF
  1. Scorecards

Initiatives and Action items

Last updated 2 months ago

Was this helpful?

While will show you progress over time, Initiatives can help you coordinate your team members, prioritize tasks, and ensure that everyone is adhering to the same standards and meeting deadlines.

Initiatives allow you to prioritize specific rules within a Scorecard and set deadlines for higher priority tasks. Cortex will notify owners and team members when deadlines are approaching, so once you set up an Initiative, everything else is handled for you.

For example, your Scorecard may have a rule that measures whether each service has an on-call rotation configured through PagerDuty. To make sure that all services actually have active on-call rotations within 30 days, you could create an Initiative with a due date in 30 days, which will notify entity owners if they need to take action on their entities.

Initiatives offer a streamlined view into the most critical tasks, improving not just the efficiency of your team members, but the accountability of your teams as well.

Create an initiative

Step 1: Configure the Initiative's basic details

  1. Click Create Initiative in the upper right corner of the Initiatives page.

  2. Choose the Scorecard that the Initiative is attached to.

  3. Start configuring the form:

    • Name: Add a descriptive name.

    • Description: Enter a description to help make the Initiative's goal clear.

    • Notifications: Click the toggle to enable notifications for the Initiative's due date.

      • Configure how often to send progress notifications. You can also designate one or more reply-to email addresses.

Progress notifications can enhance both short-term and long-term Initiatives. For example:

  • Initiative owners can set daily progress notifications for short-term Initiatives so team members have clear goals each day for completing time-sensitive action items.

  • Initiative owners can set bi-weekly or monthly progress notifications for an ongoing, long-term Initiative so team members continue to make progress on action items over time.

Step 2: Define the Initiative's goal

    • Scorecard level: To satisfy level-based Initiative, owners must meet all of the rules for a level. This is a good option if your goal is to bump all entities up to a similar level on your ladder.

      • For example, to get all entities into a production-ready state, you might use a level-based Initiative to motivate your team to configure PagerDuty and add runbooks for every entity they own by the end of the quarter.

    • Rules: Choose this option to focus on specific rules. This may be a better option if you have targeted goals that your team needs to achieve.

      • For example, if most of your entities are already in a production-ready state, you might only need PagerDuty to be set up for some of your entities.

  1. Under Due date, select a deadline for the Initiative.

Step 3: Finish the Initiative configuration

  1. Under Apply to specific entities, add one or more entity types that this Initiative should apply to. If left blank, it will apply to all entities.

  2. Optionally, click to expand Advanced options and further refine which entities this Initiative applies to. You can include or exclude groups, or add a CQL expression.

  3. Choose whether to keep your Initiative in draft form, visible only to users with the Edit Initiatives permission.

    • To keep it in draft form, enable the toggle next to Save as draft.

  4. Click Create Initiative.

When you create an Initiative, all of the owners with outstanding action items will be notified by Cortex. Users who own an entity that's already met the rule or achieved the action item will not be notified. Those who own multiple entities will receive a notification outlining any entities with an outstanding action item.

Edit Initiatives

To edit an Initiative:

  1. Navigate to an Initiative page then click Edit in the upper right corner.

  2. Make any desired changes.

  3. At the bottom of the page, click Save Initiative.

View Initiatives

View the Initiatives list

By default, the page displays a list of active Initiatives at your organization, including their description, associated Scorecard, progress level, and deadline. To view expired Initiatives, click the Expired tab.

View individual Initiatives

From the Initiatives list, click into an Initiative to view its details page.

By default, this page will open to the Failing tab, where you can see each entity's progress in the Initiative. Each row displays how many rules out of the total are passing for that entity. Click an entity to expand the view and see which rules are failing:

Once entities have completed all action items, they will appear under the Passing tab.

View Initiative action items

This tab lists the entity, the failing rule, the associated Scorecard or Initiative, the due date (if it's linked to an Initiative), and the priority based on Scorecard level.

By default, action items are sorted by priority level. Tasks with deadlines are sourced from Initiatives; those without deadlines are sourced from failing Scorecard rules.

Filter and sort action items

  • In the upper right corner of the list, click Priority to choose a different sorting method. You can select priority, name, source, or rule.

  • To filter by Scorecard, Initiative, or group, click Filter.

  • To group actions by entity, click Display then enable the toggle next to Group by entity.

Grouping by entity gives a clearer view of how many tasks are associated with each entity, giving developers an easy target for improvements.

In the Initiative creation form under Define goal, select the level or rules to prioritize. The levels and rules available are based on the associated Scorecard.

If notifications are enabled, users will receive reminders of pending action items 7 days and 1 day before the due date. This date will also be reflected in action items on the .

Initiatives in draft status will not appear on entity pages or in actions on the , and will not trigger notifications.

The new Initiative will also appear on the .

To view Initiatives, navigate to in the main nav.

You can find all outstanding tasks for Initiatives related to entities you own on the under the Action items tab:

dev homepage
dev homepage
Initiatives page
Scorecards > Initiatives
Developer homepage
Scorecards
Click Initiatives in the main nav.
The Initiatives page displays failing entities by default.
Click an entity to view its failing rules.
Click Action items on the dev homepage.
Filter and sort in the upper right side of the Action Items section.