Skip to main content
Updates released in Cortex in 2021, newest first.
IntegrationsCQLGitOpsSettings & Permissions
🔎  Query Builder Helper: In the query builder page, we’ve added a “CQL Builder” button. You can use this (familiar) builder to generate a CQL query, letting you use the Query Builder and explore the catalog without actually needing to know CQL syntax.🖥️  Github Webhook: Users of our GitHub app have been able to use the GitOps model with the pre-configured webhooks. Now, with support for org-wide webhooks, you can use our GitOps model even if you’re using a Personal Access Token or if you have multiple GH orgs! To get started, check out the instructions for webhooks in Settings → Github.
ScorecardsCatalogIntegrationsCQL
🔎  Query Builder: This long awaited feature is released! CQL in Scorecards has been a powerful way to tap into all the data about your services in an unprecedented way – ownership, third party data sources, custom data, and more. With Query Builder, you can now use CQL to query your catalog data ad-hoc, giving you the ability to explore service data across all your integrations. For example, if you’re affected by the log4j vulnerability, you can use the query builder to say “show me all the services that haven’t been deployed since last Friday and are written in java”.⭐ To get started, visit https://app.getcortexapp.com/admin/queries and try running a query!Note: Admins/Managers of Cortex can run queries that use third party integrations (git, oncall, etc). All users can run queries that access Cortex data (service details, custom data, etc).
ScorecardsCatalogIntegrations
🔔  Single Service Evaluation Slack Notifications: Whenever a single service is reevaluated due to an updated YAML file, we’ll send you a slack notification highlighting how the change affected your scores. If your scores did not change at all, you will not receive a notification.🖥️  Deploy Filters: In the Deploys page for a service, you can now filter based on type, environment, and custom data.🔗 Share Link for Scorecards Page: You can now share a link with your selected filters on the Scorecards page, making it easier to collaborate with your teammates 👯
ScorecardsCatalog
Scorecard Library Improvements: On the scorecards library page, you’ll now see both included & excluded service groups for all Scorecards.Service Group Autocomplete: Previously, the service group autocompletes showed all service groups that have been used historically, regardless of whether or not they were currently used for any services. We now only show the service groups that are active, making the autocompletes more manageable.Dropdowns: You’ll notice that they’re all alphabetically sorted now! Hooray! It’s the little things.
ScorecardsCatalog
Single Service Evaluation: While scorecards have always evaluated on a 4 hour schedule, Cortex now automatically re-evaluates the scorecards for a single service when an updated YAML file is detected! This means that the feedback loop from change -> score update is much shorter ⏱️✍️ Default Draft Scorecards: We’ve made it easier to test out Scorecards before publishing them - all new Scorecards are marked as drafts by default. We noticed that many users were developing test scorecards that resulted in a lot of noise for the rest of the organization, including notifications being sent out to service owners for a scorecard they were not even aware of!👨‍👩‍👧‍👦 Bird’s Eye Filter By Team: You can now filter the results by team on the Scorecard heatmap view. This allows you to drill down on how services are performing per team.
ScorecardsCatalogCQL
📚 CQL Documentation: We heard you loud and clear, CQL is extremely difficult to understand. We’ve released V1 of our documentation.🎯 Service Scorecard Page: It can be hard to figure out what the next steps for a service are - you have to look at all the Scorecards that apply to it and figure out what rules are failing and which to prioritize next based on levels. We’ve made this a bit easier with the new Service Scorecards Page. In the service catalog, you can now click on “Scorecards” tab which is right below the homepage. This page will show you all the scorecards for the service. When you select a Scorecard, you’ll see the next steps based on the ladder levels defined for the Scorecard as well as all the failing & passing rules. To see the full Scorecard progress page, just click “View all details”.
ScorecardsCatalogIntegrationsGitOps
🥇 Team Leaderboard: We’ve added a Leaderboard for the teams library! The leaderboard is calculated from the average of scorecard scores for all services owned by the team. Change in rank is based on the team’s score 7 days ago. You can also select a specific Scorecard to see the Leaderboard just based on that Scorecard’s scores.🐛 Rollbar Integration: You can now view Rollbar errors directly in Cortex and define Scorecard rules using Rollbar RQL queries. To get started, add your subdomain and token in the settings page. Connect your Cortex service to a Rollbar project in your cortex.yaml by adding the following:
Then you can define scorecard rules using numerical RQL queries such as rollbar.rql("select count(*) from item_occurrence") < 100👥 Azure DevOps: We’re beginning to rollout full Git integration with Azure DevOps. Now you can import your Azure DevOps projects as Cortex services.🔑 Custom Data Key Autocomplete: When you create a new Scorecard rule for Custom Data, you’ll now see a dropdown with all available custom data keys for your workspace (across all services).💯 New Scorecard Rules:
  • Pagerduty: You can check the number of users in your escalation policy that don’t have your preferred contact methods set: oncall.escalations.users_without_contact_methods(allowed=["SMS", "PHONE"]).count <= 0
ScorecardsEng IntelligenceCatalogIntegrationsAPI
🤖 Slack Bot /links command: The Slack Bot can send you back links of any type! Simply type in /cortex links metrics <service-tag> where “metrics” is the link type and you’ll see all links of type metrics! We’ve also added two new “standard” link types - metrics & healthcheck - although as always, you can input any type for your link.💻 OpenAPI Links: Any links of type open API now take you to the API Explorer, instead of linking you out to the actual spec.🔁 Incoming Dependencies: In the Dependencies tab for a service, you’ll now see both incoming and outgoing dependencies for the service. To see the full graph, just click the “View Graph” button and you’ll be redirected to the graph with that service selected.🪜 Ladders in Public API: When you use the public API to fetch Scorecard Scores, you’ll see the ladder level returned in the response as well.
ScorecardsCatalogIntegrationsGitOpsInitiatives
🪜 Ladders in Initiatives: When you create an initiative, you can now select a specific Scorecard ladder level to target, rather than selecting a specific set of rules.👣 Next Steps for Services: If you’ve created Scorecard Ladders, the service details page in a Scorecard now shows the rules to complete next in order to achieve the next level.📝 Draft Scorecards: In the Scorecard Builder, you’ll notice a new toggle to mark a Scorecard as a draft. This allows you more flexibility as you’re iterating on a new Scorecard and testing out some new rules. The draft Scorecard will be hidden for all users from the service homepage, the scorecards library, and the reports page. All admins can see the draft Scorecards by clicking on the “All Scorecards” tab and clicking “Show drafted scorecards”🏗️ Service Template Stats: We’ve created a stats page for service templates so that you can see what services have been created from which templates.🐶 Datadog Improvement: We now support multiple tags for DataDog monitor / SLO lookup:
💯 New Scorecard Rules:
  • Ownership: check that a service is owned by groups rather than individuals.
  • Dependencies: count the number of cycles
  • Git: check whether file contents match a checksum
ScorecardsCatalog
🪜 Ladders: Each Scorecard can have levels to aspire to, by defining a progression of rules from one level to another. This means you can categorize rules in your Scorecard into “beginner/intermediate/advanced”, or “bronze/silver/gold/platinum/all-star”, giving service owners an immediate understanding of priority and a new form of gamification 🕹️Some highlights:
  • A ladder can include as many levels as you desire!
  • The service has to complete all rules for a level (and all the levels before it) to receive the badge for that level.
  • The color of the badge for each level is customizable.
  • Cortex provides birds eye reports for levels, just like scorecard scores.
To get started:
  1. Open your scorecard in Cortex
  2. Click “More Actions” → “Add Ladder”
  3. Add a new level, and set the rules (the levels are in ascending order, as in, “beginner” is first in the list and “advanced” is third)
Please let us know if you have any feedback or run into any issues!👯 Automatic Team Creation: Now when you tag a service with a team from your identity provider, we’ll automatically provision the creation of a new corresponding Team in Cortex, if it doesn’t already exist.⁉️ Scorecard Custom Error Message: Cortex already lets you define descriptions for rules using markdown, and now you can display a different message in the failure case – for example, to describe why the service may have failed the rule, or to link to an internal document outlining how to fix the issue.
Catalog
👣 Progress Indicator: This is just a small UX tweak, but we’re really excited about this! Previously, it was impossible to know where you were in multi-step flows throughout Cortex, like the new service creation flow. We’ve added progress steps to the top of the page so that you know exactly where you are and how many steps are left.🍪 Service Creator Confirmation: In the service creation flow, we’re adding a confirmation page before you submit, so that you can review all the input data and confirm that everything looks good. If it doesn’t just use the previous button to go back and make the necessary updates.
ScorecardsCatalogIntegrations
👯 Teams: We’ve been working on this for a while and we’re really excited to share this with you all! All of your teams can now have their own homepage in Cortex! Every team will be able to create a page to share their team charter, links, view members of the team along with titles, share scorecard scores, and more.On the left hand side, you’ll see a fancy new “Teams” icon under the home button. Click that to go to the Teams Catalog and start creating a new team. Based on your integrations, you’ll have the ability to import groups from your IdP as teams, meaning the team members stay in sync automatically. After going through the creation flow, you’ll be able to see the new team with all the information you added as well as its members.🧞 Opsgenie Teams: If you’re using Opsgenie, you can now use Opsgenie Teams as a service ownership provider (similar to GitHub Teams and Okta groups). You can also import these teams into our brand new Teams page.
CatalogIntegrations
Slack Dependencies Command: We’ve added a command that allows you to see first-level incoming and outgoing dependencies for a service. To try it out, type “/cortex dependencies <service-tag>” in Slack.Let us know if there’s a specific command that you’d like to see added.
ScorecardsCatalogIntegrationsAPI
OpsGenie Alerts in the Timeline: On the service timeline page, you’ll now see the alerts for the previous week, their statuses, and messages.All Scorecards Reports Improvements: In the reports page, you can now sort & filter the “all scorecards” reports. Additionally, we’ve added an average score column.Scorecards Service Scores API:You can now use the Scorecard API to fetch scores and metadata for all your services with just 1 HTTP request! https://cortexapps.github.io/openapi/#/public-scorecard-controller/getScorecardServiceScoresPackages API:You can now send .NET Nuget packages through the API, allowing you to create scorecard rules on top of them.
ScorecardsCatalogSettings & Permissions
Owner Descriptions: Now you can add labels for email owners for teams. For example, if your team has a PM that’s outside the specified LDAP team, you can manually add their email and name along with a description of their role. Or you can use the description to add any sort of qualifying information to those external members.JQ Scorecard Builder Rules: We’ve added new rules in the Scorecard builder to parse custom data with jq expressions. You can pipe arbitrarily custom JSON blobs and tease out whatever service data you need using number and boolean jq expressions.Git Default Branch Rule: You can now validate that repositories follow company style for Git default branches using a new Scorecard rule. You can also validate that it matches any arbitrary regular expression.Track Service Template Adoption: We’ve added a running counter for how many times a service template has been used. This allows you to watch how best standards and practices are adopted across your organization.
ScorecardsCatalogIntegrationsCQLSettings & Permissions
All Scorecards Reports: In the reports page, you’ll be able to see a bird’s eye view of how all the scorecards are doing for each service. You can also group by teams or service groups to see what the Scorecard score average for their services is.Custom Integrations: Cortex already allows you to push in Custom Data to be used in Scorecards. We’ve released support for a new integration pattern: For each data source, you can create a unique URL (under “Settings → Custom Integrations”) and define a jq command that defines where in the payload Cortex should look for the service identifier. We’ll then automatically map that payload to the service’s Custom Data.This lets you connect to new integrations (like on-prem or internal tools, webhooks, etc) without having to write tooling to parse and push data to Cortex – just send Cortex the payload and we’ll figure out the rest!Descriptions for API Keys: When you create an API key with Cortex, you can now add a description so that you know what it’s being used for.K8s Cluster Name Scorecard Rule: We now support the ability to check for the cluster name of a given Kubernetes Resource in CQL. k8s.cluster.name.matches("(.*)production(.*)")Dependency Rule: You can add a scorecard rule to check how many inbound and outbound dependencies a service has.
Catalog
Service Page Improvements: The service pages are getting a small makeover 💄 to make them a bit more intuitive to use & consistent with the rest of the app.Dependencies: We’ve added a button on the top right of the Dependencies page which will take you to a view of the dependency graph, centered on the service you were viewing.
ScorecardsCatalogIntegrations
Slack Search Command: We’ve added a command that allows you to search through all your services. For example, if you type “/cortex search brain”, you’ll see:Open Policy Agent Support in Scorecards: We now support complex OPA programs to validate custom JSON. You can push arbitrary service data from CI or external integrations and can parse and validate them through expressive OPA policies.K8s Support for StateFul Sets and ArgoCD Rollouts: We now support ArgoCD Rollouts, and Kubernetes StatefulSets to map Cortex Services to K8s Installations. Metadata regarding the infrastructure will now be surfaced on the service k8s page, and can also be used for scorecard rules!
CatalogIntegrationsCQL
JQ Expressions: We’ve added support for jq expressions within CQL. Combined with JSON blob custom data, you can write queries like jq(custom("my-key"), "reduce .[] as \$item (0; . + \$item)" > 12 and validate arbitrary custom JSON.Slack Commands: We’ve added two new Slack bot commands:
  • /cortex service <service> - Lists service information such as owners, oncall, links, and timeline events
  • /cortex timeline <service> - Lists recent timeline events
Long running slack commands like the service command also don’t timeout anymore, and would return the results to the invoking channel as soon as they’re evaluated!
ScorecardsCatalogIntegrationsGitOpsSettings & Permissions
Async Scorecard Progress: You can now watch scorecard calculations in real time when initiated by users, so calculation time is no longer a black box.Datadog SLOs and Monitors lookup by tag: You no longer need to manually define SLO and Monitor IDs in your cortex.yaml file! Cortex will automatically look up monitors and SLOs from Datadog if they’re tagged with service:<service tag>, where the “service tag” is the service identifier you’ve used in Cortex (the x-cortex-tag field).Team Progress per Rule in Progress Report: You can now break down how your teams or service groups are doing in service quality over time even further by selecting a specific rule in your scorecard on the progress reports page.Automatic Role Based Permissions: Currently all new Cortex users are created with minimum permissions, without the ability to edit scorecards or access the settings page. We’ve just released a feature that allows you to auto-map LDAP groups to roles, so when a new user is created, they’ll be created with the role corresponding to groups they’re a part of within your identity provider.
ScorecardsCatalog
Scorecard Rule Titles: Scorecards help establish best practices and understand your service quality - but it’s sometimes hard to understand the scorecard rule and why its important from just the expression. Now you can add titles in addition to descriptions to each scorecard rule. Rule titles and descriptions help engineers, both experts and newly onboarded, understand why a rule is important or how to fix it if it’s failing.To add a title, click “Edit Scorecard” on the scorecard page and select the rule you want to add a title for. If you don’t have access to the “Edit Scorecard” button, ping your admin to add titles to rules.Tip: Rule titles and descriptions support links and markdown formatting - use this to link to internal wikis for additional details!Reports Overhaul: We’ve united all the reports views into one page - when you click the reports icon on the left, you’ll see the three different types of reports (bird’s eye, progress, and report card). You can select whichever one you want to see and share links to each with your team.The view report button for scorecards will bring you to this view as well.
CatalogIntegrations
New Features for Edit Service Page: We’ve added the ability to connect a Github repo with the service if you have Github configured in Cortex. We’ll also hide any sections that are not relevant, based on the integrations you’ve set up in the Settings Pages.Service Tag Lookup: You can quickly look up a service by going to: https://app.getcortexapp.com/admin/index?tag=serviceTag. If the service exists, we’ll redirect it automatically. If it doesn’t we’ll just fill in the search bar with the query.
CatalogInitiatives
Edit Service Page: If you have UI editing enabled, you probably noticed that editing multiple fields for a service requires navigating to many different tabs (links, oncall, etc) - We just rolled out a brand new unified “Service Edit” page that lets you modify as many fields as you need on one screen. You can edit service details, owners, links, dependencies, and on call for the service at the same time.We would love to hear your feedback in the comments!Export Initiative Data: In the “More Actions” dropdown for initiatives, you’ll now be able to copy initiatives data to CSV by teams.Sidebar Updates: We’ve updated the icons on the left hand side and changed the order, hopefully the flow makes more sense. The service graph now lives below the service homepage and you’ll see a nice new icon for the help desk on the bottom left.
CatalogIntegrationsGitOps
Opsgenie Wildcard Support: We added the ability to tie Cortex Services with arbitrary metadata from Opsgenie Alerts. You can now specify a list of key-value pairs to tie Cortex Services with Opsgenie Alerts by adding this into your YAML:
For more information, take a look at our docs.Graph Facelift: We’ve updated the design of the Graph Page to make it more consistent with the rest of the app and easier to use. Love it? Hate it? Have ideas for improvements? Let us know!
ScorecardsCatalogIntegrationsGitOps
Atlassian App: Cortex is now officially an Atlassian Marketplace partner! Find our published Atlassian Connect app here. With the installation comes automatic parsing of cortex.yaml files as well as all of our Bitbucket features for Scorecards and the Service Catalog.Reports Facelift: We’ve updated the design of the Reports Page to make it more consistent with the rest of the app and easier to use. Love it? Hate it? Have ideas for improvements? Let us know!Graph Improvements: The default graph is now “klay” - to change it, just select the dropdown on the top left of the graph. The “Share Link” button in the graph page will now include the Graph type to ensure that whoever receives the link sees exactly the same thing.
ScorecardsCatalog
Statistics in Scorecard Report by Teams or Service Groups: A few weeks ago, we released the ability to select a team or service group in a Scorecard’s progress graph to help understand service quality over time.Under that chart, you’ll also see a table with a breakdown by team / group with the average, median, min, and max scores for the teams during the selected duration, giving you a better understanding of historical progress for teams.If you only want to see specific groups or team, you can filter by those and the entire report now updates to show you only top & worst services for the selected filters.You can also collapse this section if you just want to see the report below.Search Improvements: If you’re using specific user emails in addition to owner groups, you can now filter by these on the homepage.
ScorecardsCatalogIntegrationsGitOps
Absolute Points in Scorecards: Currently, we display all Scorecard scores as percentages throughout the app. We’ve enabled the ability to view this as absolute scores instead - If you have a scorecard that has rules adding up to a total of 20 points, you’ll now be able to see the points value for each service (ie 15 instead of 75%).To switch your workspace to absolute scores, go to App Preferences in the settings page and toggle “Show absolute scores in Scorecards” to true. This is a company-wide setting, meaning that everyone in your workspace will see the same thing.Embed checked in OpenAPI specs: Previously, the only way to embed OpenAPI specs was through the cortex.yaml file or a raw URL publicly available on the internet. Now, you can define a relative link to a spec from your Cortex service’s Git repository like:
Infer Jira Components: For services with unmapped Jira labels/components we now auto-guess Jira tickets based on components matching your Cortex service’s tag.
ScorecardsCatalogIntegrations
Scorecard Progress Report Chart by Teams or Service Groups: Understand how your teams are doing in service quality over time, by selecting a team or service group in a Scorecard’s progress graph. You can also filter down into data for specific groups. To export the data, just hit the button on the top right.New Scorecard rules
  • NewRelic: Enforce standards around performance for your NewRelic applications, such as response time, throughput, apdex target, host count, instance count, and concurrent host count.
ScorecardsCatalogIntegrationsGitOps
Rule Descriptions in Scorecards: When adding rules to your Scorecards, you’ll be able to add descriptions to each rule. You can add a brief note about what the rule does, why it’s important, or whatever else your heart desires.Dependency Metadata: Through the YAML, you can add arbitrary fields to any dependency and we’ll show it to you in the Dependencies tab in the UI.
New Scorecard rules
  • Deploys: Check the number of deploys with a certain status, such as FAILED, within a specific lookback window.
  • OpsGenie: Check the number of alerts that match a specific query within a specific lookback window.
ScorecardsCatalogIntegrations
ECS Events in ECS service tab and timeline: If you have the ECS integration set up, you’ll be able to see ECS events in the service tab as well as in the timeline alongside other service events, such as Git commits, Sentry issues, and Pagerduty incidents.Improved visibility into service scores in Scorecards: When you select a service in the Scorecards page, you can see which rules the service is failing and historical details for each rule. When you hover over a failing rule, you’ll also be able to see the current value for each rule. For example, if one of your failing rules is sonarqube.metric(“coverage”), on hover you’ll see what the current coverage is.New Scorecard rules
  • GitLab: Check the number of open vulnerabilities that match a specified severity level
ScorecardsCatalogIntegrationsGitOpsInitiatives
JIRA On-Prem: Were you sad when you saw the JIRA integration but couldn’t use it because you have an on-prem version? Worry not - the on-prem version is here. Go to the settings page, switch to on-prem, and add your login information. After you do so, you can create scorecard rules for issue counts using JQL — answering questions like “how many open customer facing issues does my service have?” We map issues to services by labels, and by default the Jira label will be your service’s tag, but you can manually override in your cortex service descriptor like:
Bugsnag On-Prem: We recently added support for Bugsnag on-prem. Add the host in the settings page and you’ll be able to add Scorecard rules to measure operational maturity through the number of open issues.Custom Data: Custom metadata is a powerful feature of Cortex that lets you augment built in integrations with your own data about services. Cortex can now support JSON blobs (like arrays and objects) in addition to boolean/string/numeric/semver values. As a follow up, you’ll be able to use this data in scorecards using jq!Initiative Creation Notifications: On Initiative creation, we’ll send Slack messages to service owners with all of their upcoming action items, so they’re aware of ongoing migrations and organizational initiatives.
ScorecardsCatalogIntegrationsGitOps
Scorecard Builder: It’s no secret - our old scorecard editor could be confusing to use and made it difficult to explore all the different rules that were available to use. We’ve rolled out a completely overhauled scorecard editor that’s far more intuitive and makes discoverability of rules easier. When adding a new rule, you now start by choosing a specific integration, like GitHub or “Cortex Built In”, and we’ll show you which rules are relevant to your integration of choice!BambooHR: You can use BambooHR to keep ownership of services up to date. To get started, add your subdomain and token in the settings page. Afterwards, you’ll be able to set the BambooHR departments as team owners in the service descriptor!
ScorecardsCatalogIntegrationsInitiativesSettings & Permissions
Reports: We’ve added a nice “Report Card” looking icon in the sidebar, click it and you’ll see our brand new reports page! You can select a scorecard and see a breakdown by team or service group of how your services are performing. It makes it incredibly easy to understand areas for improvement. You can copy the data to CSV to put it in Excel if you need to configure it further.Nudges & Notifications: If you have Slack configured, Cortex will message service owners about pending initiative action items and send a weekly report that includes improvements and drastic drops in scorecard scores for services. Users can unsubscribe at any time from the Settings page.Instana Integration: You can now use Instana for service discovery. Add your API key and we’ll auto-detect all Instana services, so you can quickly onboard all of your services at once.
ScorecardsCatalogIntegrationsAPI
Google Groups support for Ownership: Google Groups support for ownership has been rolled to all users! You can now use Google Groups as a source of truth for team memberships. Start by setting up your Google API credentials in Settings, and adding the group as an owner (like “infra@getcortexapp.com”). All the members in the group will see their “My Services” page update automatically!Scorecard Reports Improvements: We’ve added a progress graph to the Scorecard reports along with a date filter. You can configure the timeline of your report from just two weeks ago to three months ago.New Scorecard rules
  • Datadog: Check the number of datadog monitors or that it matches a specified regex pattern.
CatalogIntegrationsGitOps
Kubernetes Multiple Cluster Support: We’ve enabled the ability to install the K8s agent on multiple clusters, and connect multiple deployments to a service. You can distinguish deployments by cluster, name, and namespace. Details for the selected cluster will be displayed at the Kubernetes integration page.Email us at team@getcortexapp.com to get access to the Cortex K8s agent. Afterwards, you can add identifiers and clusters for each deployment in a service YAML:
AWS Multiple ECS Support: We’ve also enabled the ability to connect multiple AWS ECS containers to a service. Details for the selected container by ARN will be displayed at the ECS integration page.To get started, make sure you have ECS configured. Afterwards, you can add cluster and service ARNs in a service YAML:
ScorecardsEng IntelligenceCatalogIntegrationsGitOpsSettings & Permissions
Lightstep SLOs: You’ll be able to define SLOs for latency metrics on any arbitrary streams, at different percentiles. Here’s how it works:
  • For a given stream, you can define a target latency threshold (e.g. 200ms) and the percentile (99th). Latency for stream <x> at 99th percentile should be less than 200ms. You can define multiple percentile+target combinations for each stream.
  • For each percentile/latency target combination, you can define an SLO
  • Because Lightstep doesn’t support true event-based “SLI”, we treat each timeslice (1 minute) as an “event” for SLI calculation.
You can get started by adding your API key in the settings page and adding a stream + SLOs in a service YAML:
  • Alerting when SLO is breached
  • Visualizing error budget
  • SLO dashboard to see all SLOs at a glance
  • Error + throughput SLOs
  • Longer lookback period (currently 7 days)
Events Timeline: When looking at a service, the events tab will show github, deploys, sentry, and pagerduty events. You can filter by dates or event types.K8s Import: Allows you to see if there’s anything in your cluster that hasn’t been imported (or auto-mapped to a service), and import them easily from that page. You can find it in the K8s settings page.New Scorecard rules
  • Lightstep SLOs: Check if all SLOs are passing or the number of SLOs defined (so that you can track adoption of SLOs throughout the engineering organization)
ScorecardsCatalogIntegrationsAPIGitOpsSettings & Permissions
JIRA Integration: To get started, add a personal API token in the settings page. After you do so, you can create scorecard rules for issue counts using JQL — answering questions like “how many open customer facing issues does my service have?” We map issues to services by labels, and by default the Jira label will be your service’s tag, but you can manually override in your cortex service descriptor like:
Trigger a Pagerduty Incident: Go to the on call tab for a service, add a title, a few details, and confirm your Pagerduty email. Once the incident has been triggered, you’ll be able to go to it in Pagerduty if you choose. If you have an existing API key in Cortex, you’ll need to update it to have write access before using this feature.New Scorecard rules
  • K8s Integration: Check if your K8s deployment has a label or the label matches specified regex. The labels are being pulled from the metadata object on the spec.
  • Git: Check if a package exists.
Last modified on November 18, 2026