Skip to main content
Updates released in Cortex in 2023, newest first.
CatalogIntegrationsAPIGitOpsInitiativesSettings & Permissions
Improvements 📈
  • We’ve made various improvements to On-call Assistant, including:
    • Guessing the service an incident relates to in cases where explicit configuration does not yet exist
    • Better display of messages when an incident is triggered for a large number of Cortex services
    • Sending Slack messages to on-call users that have not logged into Cortex yet
  • We’ve added support for using an entity’s ClickUp list during the initiative issue creation flow. You’ll now see a toggle in the “create issues” modal to “use list defined in entity YAML.” If this option is selected, it will create issues in the YAML’s selected list, otherwise it will create a new initiatives list in the space/ folder mapped to the entity to store all Cortex created tasks.
  • We’ve added a trigger incident button to the incident.io page for an entity
  • You can now fetch Slack channels and other ownership information for entities in the public API
  • We’ve added support for custom tag keys for NewRelic dependencies
  • You can now edit names and descriptions for personal access tokens and API keys
  • We’ve added initiatives to audit logs
Bug fixes 🐛
  • We’ve fixed a bug with automatic discovery of dependencies
  • We’ve fixed an issue with duplicate teams showing up in the dev homepage
  • We’ve fixed a bug with the calculation for onboarded users in Onboarding Management
  • We’ve fixed a bug with ServiceNow presenting no discovered services
ScorecardsEng IntelligenceCatalogIntegrationsAPICQLGitOpsSettings & Permissions
Improvements 📈
  • We’ve overhauled our import entity page to make it consistent across all entity types. Please let us know if you have feedback!
  • We’ve added entity counts to the teams entity tab to make it simpler to understand what a team owns
  • We’ve updated the Wiz issues page to show you more information about how to remediate these issues as well as the subscription name and potential impact
  • We’ve added an AWS account ID filter to the resources catalog and discovery audit
  • On-call Assistant now supports service lookup via PagerDuty Escalation Policies, in addition to Services
  • We’ve added GitOps logs to the public API
  • We’ve added the CQL report description to the details page
  • Notifications will now display time in your timezone instead of PST
  • You can now see changes to custom roles in audit logs
  • We’ve updated the LaunchDarkly descriptor in the YAML for ease of use. Please note that this is a breaking change. While we usually avoid breaking changes in the YAML, we felt that this change significantly simplified the YAML and improved experience.
Bug fixes 🐛
  • We’ve fixed an issue that was causing duplicate notifications to be sent out occasionally
  • We’ve fixed a bug with the NewRelic dependency sync timing out
  • We’ve implemented a fix for rate limit errors when using Datadog metrics in Scorecards
  • We’ve fixed an issue with the user mappings table that was causing the page to crash when there were too many users
ScorecardsEng IntelligenceCatalogIntegrationsGitOpsSettings & Permissions
Eng intelligence: Last week, we announced a new offering to help you further improve software health and operational efficiency. If you’re a Cortex account owner, you’ll notice a new item in the Cortex main header labeled “Eng Intelligence.”Here you’ll find critical metrics like deploy frequency, average time to review, and weekly merged PRs. Use this data to uncover bottlenecks and add or update goals in Scorecards to unblock your team.While this is an add-on module, you can take a tour with sample data to preview the insights you’d see if you decide to connect GitHub, GitLab, PagerDuty, or deployment and rollback data. Check out the docs, and connect with your Cortex Customer Success Manager to learn more!incident.io integration: We’ve added incident.io to our list of integrations! You can now see incidents for your entities and include them in Scorecards. To set it up, simply add your API key in the Settings page and add custom data fields to your YAML files in the x-cortex-incidentio section. After doing so, you’ll be able to see incidents in the entity details page and write Scorecard rules for them. Take a look at the docs for more information.Improvements 📈
  • We’ve updated the logic for “My domains” to include only domains you actually own. You’ll no longer see domains for services and resources that you own.
  • We’ve added a “Refresh Jira issues” button in the developer homepage
  • We’ve added a degree filter to the dependency graph
  • We’ve added package support to GitOps logs
  • You can now add human-friendly names to API keys upon creation
  • You can now limit the groups we pull in from Azure Active Directory by adding a filter in the Settings page
Bug fixes 🐛
  • Overlaying rule-based Scorecards in the graph now works as expected
  • We’ve fixed an issue with the linter for the GitHub app
  • We’ve fixed a bug where we showed the external team id instead of the team name in the Teams tab for Roles & Permissions in Settings
CatalogIntegrationsAPIGitOpsSettings & Permissions
Major performance improvements: Over the weekend, we made some upgrades to our infrastructure that will increase performance and reduce spikes in latency. If you see issues, please reach out to help@cortex.io.Personal access tokens: All users can now create personal access tokens in Settings to access our public API. Personal tokens will match your own permissions.User mapping pages: We’ve added user mapping pages for a handful of integrations, including GitHub, GitLab, and Jira. With these pages, you can check the user mappings for your organization and manually add mappings for anyone who is unmapped. If any mappings are incorrect, you can also edit and remove them. With this, you can ensure that the developer homepage and other personalized pages show the correct information.Improvements 📈
ScorecardsCatalogCQLGitOpsSettings & Permissions
GitOps logs: Admins can now monitor any changes made to entities through GitOps in the new GitOps logs Settings page. If any entities have errors after processing, you’ll see a ⚠️ icon next to the YAML item in the side nav. The YAML page will show the list of errors for that entity.Scorecard rules and CQLBug fixes 🐛
  • We fixed a bug with the YAML export for Scorecards
  • We fixed a permission error when trying to edit members for a team
ScorecardsWorkflowsCatalogIntegrationsAPIGitOpsSettings & Permissions
On-call assistant: Your Cortex workspace contains lots of useful information about your service health and metadata. With On-call Assistant, we now automatically surface the most useful information when we detect an incident in PagerDuty. On-call Assistant sends a packet of information to the current person on-call who was paged, including information about the affected entity, recent deploys, ownership, and quick links to lookup more details like dependencies.Why we’re excited about this feature: On-call Assistant should help reduce MTTR, and help drive adoption and engagement with the catalog & Scorecards.Note that you’ll need configure PagerDuty in Cortex with an API access token and toggle on the “Enable On-call Assistant” option in the Settings page.We’re excited to hear your feedback as you interact with On-call Assistant! If there’s any other data you’d like us to include in the Assistant’s message or improvements to the feature, please let us know.Improvements 📈
  • You can now specify multiple Sentry projects for an entity
  • We’ve added support to add multiple custom tag keys to auto detect dependencies between services and AWS resources.
  • You can now restrict the repos from where we process team YAML files. To do so, go to the entities page in Settings and add your repository names under “Entity GitOps repository allowlist”.
Bug fixes 🐛
  • We fixed a bug with the buttons for a new service after you run the Scaffolder
ScorecardsCatalogIntegrationsAPIGitOpsInitiativesSettings & Permissions
Azure resources: We’ve added support for Azure resources! You can now import resources from Azure, see their details in the catalog, view their dependencies, and write Scorecard rules on their details. To get started, add your Azure tenant ID, client ID, client secret, and subscription ID in the Settings page. You can also configure Azure resources through the public API. Learn more about Azure resource support in our docs.Team hierarchy support for Workday integration: If you’re using our Workday integration, we’ve made it significantly easier to import your teams with their corresponding hierarchies. To get started, you’ll need to update your Workday report to include the manager and managerEmail and enable auto import of teams in the Teams tab of the Entities Settings page. Learn more in our docs.⚠️ Note: The report is synced at 4 am PST every day so you’ll need to wait a day after setting this up to see your updated hierarchy.Improvements 📈
  • We’ve added more information to the notification for when you’re going on-call. It’ll now be sent 7 days and 1 day before you’re on-call.
  • We’ve added support for using an entity’s Jira project during the initiative issue creation flow. You’ll now see a toggle in the “create issues” modal to “use project defined in entity YAML”. This will also work if the project is not defined in the YAML but we auto-guessed it. ⚠️ Note: This does not work if you’re using labels or components in the YAML, you must use projects.
  • You can now drag and drop inputs when configuring Actions
  • You can now specify custom roles for Teams permissions
  • We’ve added the Git information for an entity to the list entities and retrieve entity details endpoints
  • We’ve added a query parameter for including links in the list entities endpoint response
  • We’ve made performance improvements to the Scorecard scores table for rule-based Scorecards
  • Jira tickets in the developer homepage now show the exact status instead of the status category
Bug fixes 🐛
  • When a new user logs in for the first time, their dev homepage should be populated with entities they own and relevant PRs, Jira tickets, and action items.
  • We’ve implemented some fixes in the entity overview page for over-fetching that resulted in extraneous screen flashes
  • When the children of a domain are updated in the YAML, any removed are now properly removed from the hierarchy as well
  • We fixed a bug with deleting a role from a team
  • We fixed an issue with Opsgenie auto-discovery
  • We’ve fixed an issue where cards in the entity overview page were taking up excess height in Safari
  • We’ve fixed an error with Datadog monitors
ScorecardsCatalogIntegrationsGitOpsSettings & Permissions
Onboarding management: Admins can now see who in their organization has onboarded to Cortex and blast welcome messages to specific teams / users who don’t yet have Cortex accounts in the new onboarding management page.Slack identity mapping page: You can now check the Slack identity mappings for your organization and manually add mappings for anyone who is unmapped. If any mappings are incorrect, you can also edit and remove them.Teams from ServiceNow: We’ve added support for importing teams from ServiceNow. To see them in the discovered teams list on the import page, you’ll need to set up mappings in the Settings page for your team and team member tables as well as the table that connects the two.Improvements 📈
  • We’ve added domains and teams to the “My catalog” tab in the developer homepage
  • You can now specify custom roles when creating API keys
  • We’ve alphabetized the items in the tools dropdown so that it’s easier to find what you’re looking for
  • You can now specify whether your PagerDuty token is read-only or write in the Settings page. If using a read-only token, we’ll hide the “Trigger incident” button from an entity’s on-call page.
Bug fixes 🐛
  • We fixed a bug with links for teams on entity pages in the owners section.
  • We fixed an issue with the Scorecard rule filters if you have specified multiple groups
  • We fixed a bug with processing Scorecards from GitOps when using the allowlist
  • We fixed a bug with level-less rules in Scorecards in GitOps
ScorecardsCatalogIntegrationsGitOpsSettings & Permissions
Graph overhaul: We’ve completely overhauled our dependency graph! The nodes are much clearly differentiated, including with the entity’s icon as well as full x-cortex-tag. We’ve also updated the UX to make it more clear what filters are available, as well as added the ability to search directly on the graph.LaunchDarkly integration: We’ve added LaunchDarkly to our list of integrations! You can now pull feature flags from LaunchDarkly into the catalog and write Scorecard rules for them. To get started, add your API key and specify your region in the Settings page. Learn more about how the integration works in our docs.Improvements 📈
  • We’ve alphabetized the items in each section in the Settings page so that it’s easier to find what you’re looking for.
Bug fixes 🐛
  • If you don’t have permission to cancel a Scorecard or query evaluation, you will no longer see the cancel button.
WorkflowsCatalogIntegrationsAPIGitOps
Happy Halloween 👻Search improvements: We’ve improved the text search functionality in the Service catalog, Resource catalog, and “My entities” tab in the developer homepage. Searches will now check against more fields defined on the cortex.yaml (e.g. repository). Additionally, there is now an “Advanced search” mode, which can be toggled to enable Lucene-like syntax with support for field-specific searches (e.g. “repository:brain-backend”), explicit wildcards (”migr*”), etc.Improvements 📈
  • You can now limit AWS discovery to specific regions in the Settings page. This is helpful if you’re encountering issues with rate limits
Bug fixes 🐛
  • We’ve fixed a bug with the gitRepository filters in the list entities endpoint in the public API
  • We’ve fixed a bug with filtering in the GitHub workflows page for an entity
WorkflowsCatalogIntegrationsAPIGitOpsSettings & Permissions
AWS support for all resource types: We’ve added support for importing all resource types from AWS into the resource catalog. To set this up:
  1. You’ll have to update the permissions for the AWS role being used by Cortex. Permissions can either be configured manually for each type, or by using the ReadOnlyAccess policy that AWS provides. For example, if you want to import resources of type “AWS::IAM::Role”, we’ll need to have permission to “iam:ListRoles”, “iam:ListAttachedRolePolicies”, “iam:GetRole”, and “iam:ListRolePolicies”. Make sure to add the “cloudformation:ListTypes”, “cloudformation:ListResources”, “cloudformation:GetResource” permission so that we can pull the list of types available from AWS.
  2. In the Settings page, add the types that you would like Cortex to support under cloud control types. If you don’t see the type you’re looking for, click the “Refresh cloud control types” button and verify that your configured role has the proper permissions.
After making the Settings updates, you should see the resources for the selected types on the import resources page. If you do not see the resource you’re looking for, click the “Sync resources” button.If you have auto import for resources, the resources of selected types will be auto imported as well.Improvements 📈
  • We’ve added support for importing groups from GitLab
  • We’ve added an endpoint to GET entity descriptors to the public API
  • We’ve added support for URLs in deploys and custom events
  • You can now see all the services, resources, and domains for a team by toggling the “Include inherited children” in the filter modal
  • We’ve made various UX improvements to the teams details page such as adding parent & child information to the page, moving the hierarchy into the overview tab, and adding a modal to show the full description if it exists
  • We’ve removed the departments and hierarchy tab from the team catalog. You can see the hierarchy in the “All” tab.
  • We’ve added support for configuring PagerDuty through the public API
  • We’ve made some improvements to the content of the weekly report notification based on your feedback
Bug fixes 🐛
  • We’re now evaluating all YAML files in a PR, instead of just the ones in the last commit
  • We fixed a bug with showing the latest Go package versions for a service
  • We fixed a bug where scaffolder was not processing Cortex YAMLs in the .cortex/catalog subdirectory
ScorecardsEng IntelligenceIntegrationsCQL
New FeaturesScorecard rules and CQLImprovements 📈
  • When an authorized user attempts to log into a different tenant via query param (e.g. /login?tenantCode=xyz), we will automatically log them out and then take them into the auth flow for the target tenant
  • Updated the labeling of rule groups in the Scorecard details for an entity
Bug fixes 🐛
  • We fixed a bug with removing GitHub Oauth
  • Slack notifications properly display markdown content
ScorecardsCatalogIntegrationsAPISettings & Permissions
Custom roles: Cortex admins can now create RBAC roles outside of the default ones that Cortex provides in the roles & permissions Settings page. You can define custom roles that have specific, granular permissions to lock down certain parts of the app for certain types of users.If you don’t see a permission that you’re looking for, please let us know.Custom events: You can now create custom events for entities using the public API. These custom events will be included in the events timeline. For example, you can add custom events to track k8s configuration changes, secret changes, incidents, and more.Improvements 📈
  • We’ve added support for Slack IDs in YAML files.
  • We’ve added the source of custom data in the catalog page so that you can see if it was defined through the YAML or API.
  • We’ve updated the language in the notifications settings page to make the flags consistent with other notification flags.
Bug fixes 🐛
  • We fixed a timeout issue with the auto import for resources.
  • Entities that only have operational data from ECS will now be able to consistently see that data
  • Fixed a bug causing the incorrect time range to be shown when attempting to change the visible time range of Scorecard progress
ScorecardsCatalogIntegrationsAPICQLSettings & Permissions
Coralogix integration: We’ve added Coralogix to our list of integrations! You can now pull alerts from Coralogix into the catalog and write Scorecard rules for them. To get started, add your API key and specify your region in the Settings page. Learn more about how the integration works in our docs.Team member roles: You can now add roles for manually specified team members. To do so, you’ll have to first set up the list of roles in the Settings page.Improvements 📈
  • We’ve added Jira project information to the Jira tab for entities
  • We’re now pulling in the “new_coverage” metric from SonarQube. You can check for it in Scorecard rules
  • We’ve added domain information for an entity to the Slackbot response
  • We’ve made some improvements to our weekly notification to give you more information about how Scorecard scores changed
  • You can now fetch the audit log through the public API
  • We’ve added a warning for unicode characters in our CQL input
  • We’ve added keyboard support in the global search modal
Bug fixes 🐛
  • Fixed issue with the Slackbot when there were too many dependencies in the list
  • Fixed a few links in our integration Settings pages
  • Fixed flickering page issue when logging out
ScorecardsCatalogIntegrationsSettings & Permissions
Audit logs: You can now monitor changes made to your workspace. This audit log shows changes for entities, api keys, integration configurations, & more.On-call notification: When the person on-call changes for an entity, we’ll now notify all owners at least 30 minutes before so that you always know who’s on call.Improvements 📈
  • We’ve heard your feedback loud and clear, the tooltip in the Service Catalog got in the way more often than it provided useful information so we’ve removed it.
  • If you have a points based Scorecard, you can now see the points for each rule in the entity page for the Scorecard.
  • You can now manage subscriptions for different types of notifications for your whole workspace in the Notifications Settings page.
  • By default, Cortex maps Kubernetes deployments with a cortex.io / tag annotation to Cortex entities with the same tag. In the K8s settings page, you can now input a JQ mapping to customize that mapping behavior. See the docs for more info.
Bug fixes 🐛
  • Fixed issue with height of plugins
ScorecardsCatalogIntegrationsCQL
Scorecard rules and CQL
  • Added the ability to query git commit history. For instance, to see the number of commits to test-branch over the last 5 years, you can use git.commits(branch="test-branch", lookback=duration("P5Y")).length > 1.
Improvements 📈
  • We’ve re-organized the Settings pages and added the ability to search for particular pages by name. If you have feedback, please let us know!
  • Added the ability to apply request signatures to plugin proxy requests. To set them up, visit Settings > Secrets to set a Request signing secret. Note that when set up, the same secret is used for both Actions and Plugins for consistent signatures from Cortex.
  • Actions now support string templating for request headers, and actions now have access to global secrets. To configure secrets, navigate to Settings > Secrets. To add a secret to an action header, use context.secrets, e.g. {{context.secrets.auth_secret}}.
  • Added the ability to customize the team overview tabs (we already allow customization for other entity types). To do so, visit Settings > Appearance and use the toggle to the top right of the preview on the Entity overview tabs tab.
  • Users are now able to edit children of teams directly. Previously, in order to edit children one had to navigate to the child and edit its parents.
  • Misc performance improvements
Bug fixes 🐛
  • Links from Teams/Slack to the Dev Homepage now take users to the correct tab
  • Fixed an issue causing all rules for a Scorecard whose type had changed to succeed regardless of underlying conditions
  • Fixed an issue where a “Trigger incident” button was showing up for entities that were not applicable (entities not associated with a PagerDuty service).
  • Fixed an issue where Actions with a configurable dropdown item does not consistently apply
  • Fixed an issue with long Slack messages failing to send
  • Fixed an issue where we were generating misleading links and messages in the Weekly Report for Backstage users.
ScorecardsEng IntelligenceCatalogIntegrationsAPIInitiatives
Hi everyone; hope you’re having a good week and are ready for your weekly shiplist! Our whole company is feeling enervated after an awesome full-company offsite in sunny San Diego ✅🌴.Reminder: Our legacy public /services API was removed. Please use /catalog for all current and future use cases.Improvements 📈
  • Added ability to filter the types of Okta group types being pulled in automatically. This can be particularly helpful for preventing rate limits from Cortex to Okta during the group sync.
  • Teams can now define either parents or children in their YAML files
  • Improved resiliency of our team syncing processes
  • Added links to MS Teams messages for easier navigation from the notification to the source
Bug fixes 🐛
  • Fixed an issue where the Scorecards list on the Initiatives page can be out of date if a Scorecard was added or updated previously in the session
  • Fixed example search query lookback duration with proper syntax
  • Fixed an incorrect link to docs from the “No services” state
  • Fixed an issue with incorrect external links in the weekly report
  • Fixed an issue with the /catalog endpoint not filtering by owner correctly
  • Fixed an issue where not having GitLab releases enabled for an environment caused period errors to show up in the UI
  • Fixed an error where an entity with multiple parents cased the Executive Report page to fail with recurring errors
  • Fixed an issue reading branch protection rules for a GitLab repository when there are no approval rules set
ScorecardsCatalogIntegrationsCQL
Scorecard rules and CQLImprovements 📈
  • We’ve revamped the team leaderboard to take more information into account when generating results. A team’s leaderboard score is based off of a combination of: 1) all the entities it owns, 2) its descendant teams from the teams hierarchy.
  • If we notice that an integration configuration is no longer valid during the nightly job, we send admins a notification alerting them of the error
  • We’ve added links to our documentations in various places throughout the app to make it easier to learn about all the different Cortex features
Bug fixes 🐛
  • We fixed a bug with grouping by domains in the All Scorecards report
  • We fixed a bug with approving rule exemption requests in Scorecards
  • We fixed an issue with markdowns in descriptions for entities
  • We’ve added back the validation button in the GitHub settings page
ScorecardsWorkflowsCatalogIntegrationsAPIInitiatives
Microsoft Teams integration: Our Microsoft Teams integration is now live! To set it up for your workspace, go to the Settings page and follow the steps the setup OAuth. Afterwards, you’ll need to install Cortex’s app for Teams through Microsoft AppSource.Once you have the integration set up, all users in your workspace will receive notifications from Cortex such as a weekly notification to let you know what’s on your plate for the week as well as notifications for any new Initiatives, upcoming Initiative deadlines, and score changes for services that you own. Users can manage notifications at any time in their preferences page.Take a look at our docs to learn how to add Microsoft Teams channels to entities.Improvements 📈
  • You can now manage your IP allowlist through the public API
  • When creating ClickUp tasks for initiatives, you can now select to add the entity tag as a tag
Bug fixes 🐛
  • Scorecards will be re-evaluated for all entities edited through the UI
  • Fixed error thrown when using the Scaffolder
  • Fixed page crashing issues in the discovery audit page
ScorecardsIntegrationsAPICQL
IP allowlist: You can now restrict Cortex app & public API access to certain IPs in the IP allowlist page in Settings.Integration statuses: We’ve added a nightly job to check the status of all integrations configured in your workspace. If you’re an admin, you’ll see the status along with errors, if there are any, in the Settings pages for integrations.Scorecard rules and CQL
  • We’ve added support for .average() of durations to CQL. For example, you can now check that the average duration of a service’s crashes is less than 2 hours by doing custom("service_crashes").map((crash) => datetime(crash.start).until(datetime(crash.end))).average() < duration("P2H")
Improvements 📈
  • We’ve added support for specifying flags in the Codecov registration for an entity
  • The number of Scorecards in the tab is now updated when the draft toggle changes
  • We’ve added auto-guessing for the Bugsnag and xMatters integrations
ScorecardsCatalogIntegrationsAPICQLGitOps
ServiceNow integration: We’ve released our ServiceNow integration. Services from ServiceNow will be included in the import services page as well as the discovery report. To get started, add your instance name and credentials in the Settings page. You’ll also need to add a table mapping to let us know which tables and fields we should pull information from. Read more in our docs.Customization: You can now make your Cortex workspace your own by uploading your logo to replace the Cortex logo in the top left corner.Improvements 📈
  • We’ve made various improvements to our Scorecard linter. This should help significantly when updating Scorecards through GitOps.
  • We’ve added a domain filter to the service and resource catalogs.
  • We’ve added an endpoint to the public API to fetch an entity’s Scorecard scores.
  • We’ve added support for including custom data in the response of the list entities API endpoint. Simply add pass in includeMetadata as true.
Bug fixes 🐛
  • Team filters now take inheritance into account when filtering services and resources in the catalog
  • We’ve fixed images in the documents tab of entities
  • CQL rules related to ownership will now show more consistent results
  • Various fixes to correctly group teams for certain configurations in All Scorecards Report
ScorecardsCatalogIntegrationsAPIInitiatives
Note: We’re deprecating our services API (api/v1/services) on September 15th. All existing functionality can be found in the catalog API.Welcome messages: When new team members log in to Cortex for the first time, they’ll receive three welcome messages during the first 6 weeks after logging in. These messages will contain helpful information about Cortex and how to use it, helping them make use of the platform.Improvements 📈
  • We’ve updated the reviews tab in the developer homepage for PRs associated with a mono repo to show related services on hover instead of displaying them all directly in the table
  • We’ve cleaned up our sort dropdown to make it easier to use
  • We’ve updated the Scorecard progress chart to have 0 and 100 as the min and max for the y-axis instead of the min and max score. This makes it easier to understand the graph quickly without needing any context on the Scorecard itself.
  • We’ve updated our linter rules for NewRelic to warn users if they enter an invalid application ID
  • We’ve improved our auto-guessing for the Mend integration
Bug fixes 🐛
  • We’ve added support for forward slashes in entity tags to the public API
  • We’ve updated our logic when pulling GitHub vulnerabilities to respect the base path if it is defined
  • We’ve fixed a bug during Initiative issue creation when using ClickUp
  • We’ve fixed a bug with pulling issues from Wiz
ScorecardsCatalogIntegrationsAPIGitOpsSettings & Permissions
Note: We’re deprecating our services API (api/v1/services) on September 15th. All existing functionality can be found in the catalog API.Plugins in entity side nav: If you have plugins enabled, you can now add plugins in the entity side nav. To do so, go to the “Appearances” tab in the Settings page.Note: Plugins are only for customers.Improvements 📈
  • You can now fetch the Scorecard badge for an entity through the Public API. After doing so, you can embed this in the README file in an entity’s repository. The badge will show the Scorecard name and the corresponding level or score.
  • By default, the fetch teams method in the public API does not return teams without members. We’ve added a param to includeTeamsWithoutMembers to it.
  • We’ve added support for multiple NewRelic apps in the entity YAML.
  • If you’re using Buildkite, we’ll try to auto discover your pipelines based on your entity tag or repository name.
Bug fixes 🐛
  • We’ve updated a couple linter rules for the entity YAMLs including checking for an empty title or duplicate custom integration mappings
  • We’ve fixed some logic in the Bird’s eye and All Scorecards reports
  • We’ve updated the expiration on API keys to be at the end of the chosen day
ScorecardsCatalogIntegrationsAPISettings & Permissions
Note: We’re deprecating our services API (api/v1/services) on September 15th. All existing functionality can be found in the catalog API.Plugins in entity overview tabs: If you have plugins enabled, you can now add plugins in the entity overview tabs. To do so, go to the “Appearances” tab in the Settings page.Note: Plugins are only for customers.Codecov integration upgrade: We’ve moved to v2 of the Codecov API. This means that if you’re using Codecov today, you’ll need to remove your existing API token, create a new one in the Settings page, and add it to Cortex.Datadog multi instance support: If your organization has multiple instances of Datadog, you can now configure all of them in the Settings page or using the public API.Improvements 📈
  • Our Slack app has been published to Slack’s app store
  • We’ve added AWS & GCP support in the discovery audit so that you can keep track of new and deleted resources.
  • We’ve added support for GitHub vulnerabilities in the code & security tab for an entity
  • We’ve improved the performance of our report tables, including the Bird’s eye and all Scorecards reports
  • We’ve added support for deleting packages of different types to the public API
  • We’ve added required permission information to the GitHub settings page
  • We’ve improved the performance of our K8s metadata label discovery
Bug fixes 🐛
  • Fixed bug with the number of team members in the Team Catalog
  • Teams with 0 members are now being properly displayed throughout Cortex
  • Fixed bug with sorting of Jira issues in the developer homepage
ScorecardsCatalogIntegrationsAPICQLGitOpsInitiativesSettings & Permissions
Note: We’re deprecating our services API (api/v1/services) on September 15th. All existing functionality can be found in the catalog API.GitOps for Teams: You can now manage your teams through GitOps. To do so, toggle the UI editing flag in the App Preferences Settings page and take a look at our docs. You’ll want to put your team’s YAML files in a teams folder.Scorecards for Teams: We’ve extended Scorecards to support teams. When creating a Scorecard, you’ll have to select “Teams” as the entity category. This also includes initiative & CQL report support for teams.GCP labels for dependencies: We can now ingest dependencies from GCP based on the labels. If you’d like to override the label, you can do so in the Settings page.Improvements 📈
  • The dependency graph now includes domains.
  • We’ve updated our Jira validation to check for the correct project permissions.
  • The get dependencies endpoint for an entity now supports query parameters to get both outgoing and incoming dependencies.
Bug fixes 🐛
  • Archived teams are now excluded from the team leaderboard
  • We fixed the test API request button in our Public docs
ScorecardsCatalogIntegrationsGitOps
Improvements 📈
  • We’ve added auto-guessing for Snyk for monorepos based on the base path defined.
  • We’ve added support for Buildkite tags to the entity YAML.
  • We’ve added support for FireHydrant custom severities & conditions when creating an incident and in Scorecard rules.
  • We’ve revamped the ECS page for an entity and added information to the Operations tab.
  • Dynatrace services are now included in the Discovery audit.
  • When adding a resource manually, you’ll only see custom resource definitions in the types dropdown.
Bug fixes 🐛
  • Fixed relative links & images in embedded documents for entities.
  • Fixed SonarQube error on some entity pages, and the SonarQube integration showing up on entity pages when the integration is not configured
  • Fixed bug with searching for teams
  • Fixed an issue where failing to load the shields.io badge caused the Scorecard page to crash
  • Fixed a bug where the packages in a package-lock.json files were not being displayed in the Packages integrations section for entities
ScorecardsCatalogIntegrationsCQL
Scorecard badges: We’ve added README badges for Scorecards! To add a badge to your repository readme, go to the Scorecard page for the entity and click the copy button. The badge will show the Scorecard name and the corresponding level or score.Mend multi organization support: We now support multiple organizations for Mend. During the Settings page, you’ll have to specify “GLOBAL” for the org type and add your global org token.Improvements 📈
  • You can now overlay dependency events in the Events page for an entity
  • Documents entity page will now default to README.md if it exists
Bug fixes 🐛
  • Fixed bug when exporting a resource Scorecard with an advanced CQL query filter
  • Fixed some issues with the GitHub linter checks
  • Fixed forbidden error when deleting domain
  • Fixed bug on the teams members page where Cortex members weren’t being showing when a customer had a smaller subset of IDPs
ScorecardsEng IntelligenceCatalogIntegrationsAPIGitOpsInitiatives
Plugins in main header & developer homepage: If you have plugins enabled, you can now add plugins in the main header and developer homepage. To do so, go to the “Appearances” tab in the Settings page.Note: Plugins are only for customers.FireHydrant integration: We’ve added FireHydrant to our list of integrations! To set it up, simply add your API token in the Settings page and add your FireHydrant services to your YAML files in the x-cortex-firehydrant section. After doing so, you’ll be able to see and trigger incidents in the catalog page and write Scorecard rules for them. Take a look at the docs for more information.Wiz integration: Our Wiz integration is now in Beta! To set it up, simply add your client ID, secret, region, and auth in the Settings page and add your Wiz project ids to your YAML files in the x-cortex-wiz section (example below). After doing so, you’ll be able to see issues & vulnerabilities in the catalog page and write Scorecard rules for them.
Improvements 📈
  • You can now restrict the repos from where we process entity YAML files. To do so, go to App Preferences in Settings and add your repository names under “Entity GitOps repository allowlist”.
  • When creating an API token, you can now specify an expiration date.
  • We’ve added more information to the discovery report export like project IDs for GitLab events.
  • The dependency API responses now include the entity type
  • We’ve added the integration validation button to the Bitbucket Settings pages so that you can validate that your connection is working as expected
  • We made some performance improvements for the initiatives issue form
Bug fixes 🐛
  • Executive report date filter is properly displayed in deploys card
  • Selected repository information will now be saved when importing a discovered service from any source
  • Fixed bug where inputs in rule editor were sometimes being cleared out
  • Fixed issue with New Relic Apdex information in the Service Catalog
  • Fixed Snyk bug in YAML linter
ScorecardsIntegrationsInitiatives
XMatters integration: We’ve rolled out our XMatters integration! To set it up, simply add your credentials in the Settings page and add your XMatters groups to your YAML files in the on-call section. After doing so, you’ll be able to see your on-call schedule in the catalog page and write Scorecard rules for them. Take a look at the docs for more information.Bug fixes 🐛
  • Fixed bug with initiative filters
ScorecardsCatalogIntegrationsCQL
Improvements 📈
  • We’ve added an incidents section in the Operations tab so that you can see details for any active incidents
  • The developer homepage now supports multiple GitHub and/or GitLab configurations
  • We’ve added the integration validation button to the AWS, Codecov, and Prometheus Settings pages so that you can validate that your connections are working as expected
  • By default, we do not allow changing the types of entities (e.g. going from a service to a domain). If you would like to enable type changing, you can do so by toggling “Enable changing entity type” under App Preferences.
Bug fixes 🐛
  • GH app now properly checks for Scorecard level ranks in the YAML file
  • Fixed issue with CQL explorer search
ScorecardsWorkflowsCatalogIntegrationsAPICQLGitOpsInitiatives
Archival of entities: We’ve released support for archiving entities. You can still see archived entities in the catalog by toggling the “Show archived entities” toggle and navigate to their specific pages to see information but these entities will no longer be included in Scorecards, Initiatives, reports, or the dependency graph. You can also use the public API to archive & unarchive entities.Improvements 📈
  • Resource catalog shows resource type in the list so that you no longer have to rely on the icon to know it’s type
  • Scorecard evaluation information is now included in the entity overview page
  • You can now import ECS services as resources as well as use aws.details in Scorecards
  • If you’re using GitOps to manage Scorecards, we’ll now comment on PRs for the files being changed if there are any errors.
  • Scaffolder now supports multiple GitHub and/or GitLab configurations. You’ll simply have to specify the alias for the configuration you want to use when registering templates
  • If you use tenantCode as a URL param when navigating to Cortex, you’ll now be automatically redirected to logging in without having to click the “Continue” button
  • We’re now pulling in user labels from settings for Cloud SQL resources. You can also use this in CQL
  • We’ve added the integration validation button to the NewRelic Settings page so that you can validate that your connection is working as expected
  • We cleaned up the Bitbucket settings page to be more consistent with our other settings pages
  • We’ve added more examples to the aws.details section in the CQL explorer
Bug fixes 🐛
  • Fixed issue with duplicate Slack channels showing up on entity pages
  • The reviews tab in the developer homepage will no longer include your own PRs
ScorecardsCatalogIntegrationsAPICQL
GitLab multi instance support: If your organization has multiple instances of GitLab, you can now configure all of them in the Settings page or using the public API. You’ll see discovered services from all configurations in the import services page.Scorecard rules and CQL
  • Added git.lastCommit to our CQL language so that you can write rules that checks information for last commits such as datetime(git.lastCommit.date).from_now() > duration("P3D") and git.lastCommit.message.matches("^(feat|fix|docs|style|refactor|test|chore)((.+))?:")
Improvements 📈
  • We’ve extended support for importing services from multiple GitHub instances, not just your default one. As part of this change, you’ll also be able to add repositories from all instances if you have UI editing enabled.
  • You can provide a list of Kubernetes metadata label names that Cortex will use to automatically map between entities and Kubernetes resources. Take a look at our documentation for more details.
  • We added an entity tag filter to the retrieve Scorecard scores endpoint
  • If you have your workspace name bookmarked for your Cortex URL, you no longer need to press the continue button, we’ll just log you in.
  • We updated the on-call page to display all rotations from VictorOps, not just the first.
Bug fixes 🐛
  • Fixed bug with oncall != null rule in CQL
  • Fixed issue with the same Slack channels showing up multiple times in the entity pages
ScorecardsCatalogIntegrationsAPIGitOps
Improvements 📈
  • You can now use the public API to manage your AWS configurations.
  • We’ve added support for multiple Datadog environments when fetching dependencies. You can add environments in the Settings page.
  • We’ve added the integration validation button to the VictorOps Settings page so that you can validate that your connection is working as expected.
  • We’ve added support for Gitops when using Bitbucket Server with OAuth authentication. To set this up, follow the instructions in the docs. With this, Cortex can automatically parse any changes to your catalog descriptor files and other metadata on Bitbucket Server.
Bug fixes 🐛
  • Fixed bug with Scorecard YAML export where level names were not being included for relevant rules.
  • Re-creating a deleted Scorecard that had a ladder via GitOps will no longer fail
  • Fixed a couple errors when fetching ClickUp issues
  • Turned off Scorecard re-evaluation notification if score didn’t change
ScorecardsEng IntelligenceCatalogIntegrationsAPIGitOpsInitiatives
Major performance improvements: Over the weekend, we made some upgrades to our infrastructure that will result in a faster experience for you both when using the app and the public API 🚀Weekly & service re-evaluated notification revamp: We’ve completely revamped our weekly report, and moved it to Mondays to be a better experience for developers. We’ve added intelligent recommendations based on Scorecards and Initiatives to the Monday weekly report, along with information about PRs awaiting your review & Jira issues assigned to you.Bitbucket Server GitOps support: We’ve added support for Gitops when using Bitbucket Server through the use of webhooks, with support for basic auth. To set this up, follow the instructions in the docs. With this, Cortex can automatically parse any changes to your catalog descriptor files and other metadata on Bitbucket Server.Improvements 📈
  • Added filtering to the “My Catalog” tab in the developer homepage. If you’d like to save these filters, simple click the “Share” button and add it as a bookmark to your browser.
  • Added deploys graph to the Executive report
Bug fixes 🐛
  • Added the missing “cron job” service type filter to the entity K8s page
ScorecardsCatalogIntegrationsGitOpsSettings & Permissions
Redis in Resource Catalog: We’ve added support for importing AWS ElastiCache & MemoryDB. To see them in your discovered resources, you’ll need to update your permissions to include:
Improvements 📈
  • You can now restrict the repos from where we process Scorecard YAML files. To do so, go to App Preferences in Settings and add your repository names under “Scorecard GitOps repository allowlist”.
ScorecardsCatalogAPICQL
Scorecard rules and CQL
  • We’ve added support for datetime in CQL. With this, you can compare datetimes using standard comparators (<, >, <=, >=, =, !=). We’ve also added support for a .from_now() and until(datetime) functions. Take a look at our CQL explorer to learn more about how to use it.
Improvements 📈
  • Groups information can now be included in the hierarchy information when you fetch all entities & an entity response
Bug fixes 🐛
  • Fixed a bug with the owners filter on the fetch all entities endpoint
ScorecardsCatalogIntegrationsAPICQLSettings & Permissions
Scorecard rules and CQL
  • You can now get the list of groups for an entity in CQL and write rules against them such as groups.any((group) => group.name.matches(".tier-."))
Improvements 📈Bug fixes 🐛
  • Fixed scrolling issues with the rule editor in Scorecard create & edit pages
  • Improvements to Sentry validation that checks for correct permissions
ScorecardsEng IntelligenceCatalogIntegrationsAPICQLGitOpsSettings & Permissions
Scorecard evaluation window customization: Currently, Scorecards re-evaluate every 4 hours. If you would like them to evaluate less frequently, you can now change that.
  • If you use UI editing to update your Scorecards, you’ll see “Evaluation window” in the metadata section.
  • If you’re using GitOps, you can now add evaluation to the YAML:
Reducing the evaluation frequency can help with rate limits.Improvements 📈
  • We’ve added groups information to the list all entities and get entity endpoints in the Public API.
  • We’ve added GitHub releases to the events page & Git page for an entity.
  • If you have Codecov set up for an entity, you can now see the code coverage details in the Codecov specific page under Integrations.
  • You can now click on the endpoint card in the Executive report to see the endpoints for each entity.
  • We’ve added the integration validation button to the SonarQube, SignalFx, & Instana Settings page so that you can validate that your connection is working as expected.
  • Scorecard rule edits are persisted when toggling between the CQL Editor and the Rule Form.
  • We’ve added an owner filter to PRs in the developer homepage so that you can filter to just your organization.
Bug fixes 🐛
  • Fixed permissions issue with seeing Actions history
  • Entities that have owners inherited from domains are no longer included in the unowned entities count in the Executive report.
  • Revamped the AWS settings page
ScorecardsEng IntelligenceCatalogIntegrationsCQLInitiatives
ClickUp Integration: We’ve rolled out our ClickUp Integration! To set it up, simply add your credentials in the Settings page and add your spaces, folders, or tags to your YAML files. After doing so, you’ll be able to see your tasks in the catalog page and write Scorecard rules for them. You can also create ClickUp tasks from Initiatives for open action items. Take a look at the docs for more information.GitHub multi instance support: If your organization has multiple instances of GitHub, you can now configure all of them in the Settings page.Improvements 📈
  • We’ve added the integration validation button to the Lightstep & BambooHR Settings page so that you can validate that your connection is working as expected.
  • You can now click on the groups card in the Executive report to see a drill down of all your groups broken down by services, resources, and domains.
  • We’ve made performance improvements to loading the team leaderboard in both the teams page & the Executive report page.
  • We’ve added a lot more examples to the CQL explorer.
Bug fixes 🐛
  • 403 errors for GitLab vulnerabilities are properly handled.
ScorecardsCatalogCQL
Domains Hierarchy in Reports: We’ve added the domain hierarchies to the bird’s eye and all Scorecards report. With this, you’ll be able to drill down into your domains to understand how each one is doing.Scorecard rules and CQL
  • We’ve added entity_type to CQL so that you can check the type for specific entities.
Improvements 📈
  • We added validation for existing entity tags so that you see the error that the entity tag already exists during the creation flow.
Bug fixes 🐛
  • Type input is disabled in the edit resource definition page
ScorecardsCatalogIntegrationsAPICQL
Hierarchy details in Public API: We’ve added hierarchy details to the Catalog API. This includes the full chain of both children and parents for an entity.On-call in Public API: We’ve added the ability to fetch current on-call information and registration for an entity to the Public API. Note that this data is fetched on the fly so excessive use can trigger rate limits from your on-call provider.Group by domains: We’ve added the ability to group by domains in the bird’s eye and all Scorecards reports.Scorecard rules and CQL
  • Hierarchy rules: We’ve begun exposing CQL rules for domain hierarchies! We’ve added support for entity_children() and entity_parents() . Both of these rules return nested objects which, in turn, contain their own children/parents respectively as well as entity metadata for the children/parents.
Improvements 📈
  • GitLab vulnerabilities info now shows up in the Code & Security tab in the overview page.
Bug fixes 🐛
  • Rule filters are included in Scorecard YAML export
  • Domains show up in query builder results
  • Fixed null error for valid empty schemas when creating resources
  • Mend shows 0 vulnerabilities instead of missing error if there are actually no vulnerabilities.
ScorecardsCatalogIntegrationsCQL
Rule filters in Scorecards: We’ve added the ability to add filters at the rule level in Scorecards. This means that instead of writing complex CQL expressions to filter out entities in the rule’s CQL, you can define them as a filter at the rule definition level – so instead of the rule displaying as passing for the service, it will show up as filtered / exempt.Scorecard rules and CQL
  • We’ve added support for two new Semver rules — lowest_version() and highest_version() — to calculate the lowest and highest version for a Semver range
Improvements 📈
  • Added filtering in assigned reviews & my PRs tab in the developer homepage. If you’d like to save these filters, simple click the “Share” button and add it as a bookmark to your browser.
  • Improvements to how we calculate Scorecards to reduce the number of rate limits we encounter. Instead of calculating Scorecard scores all at once every 4 hours, we’re spreading out the calculations across the entire 4 hour window.
Bug fixes 🐛
  • Updated some Buildkite fields to be nullable
  • Buildkite won’t appear on entities unless it is configured
  • Made improvements to auto mapping on Jira to reduce 400 errors
  • Fixed bug with team creation for a team with a tag that previously existed
ScorecardsWorkflowsEng IntelligenceCatalogIntegrationsSettings & Permissions
GitHub Workflows: We’ve extended our GitHub integration to add support for GitHub workflows to our integration. If you have a GitHub repo defined for a service, you’ll be able to see your workflows in the catalog page and write Scorecard rules for them. This enables rules that check build failure/success rates and other similar metrics on your pipelines.Note: This will require you to update your GitHub app permissions.Improvements 📈
  • Added domain filter to the dependency graph
ScorecardsEng IntelligenceIntegrations
Improvements 📈
  • Enabled filtering by departments in the Executive Report
Bug fixes 🐛
  • Fixed bug when toggling whether or not notifications are enabled for a Slack channel
  • Fixed issue with calculation of Scorecard averages when filtering by teams in the Executive Report
  • Resource and domain action items show up in developer homepage
  • Logic improvements in a Scorecard’s report card
ScorecardsCatalogIntegrationsAPICQL
CQL queries in Public API: We’ve added the ability to run CQL queries and retrieve their results to the Public API. Any queries run through the API will also be in the Query Builder.Buildkite Integration: We’ve rolled out our Buildkite Integration! To set it up, simply add your credentials in the Settings page and add your pipeline slugs to your YAML files. After doing so, you’ll be able to see your builds & pipelines in the catalog page and write Scorecard rules for them. Take a look at the docs for more information.Snyk Code Integration: We’ll automatically try to discover Snyk projects tied to your service but if you want to override our auto mapping, you can add your organization and project id along with the source as `CODE` in the YAML. Take a look at the docs for more information.SonarQube multi instance support: If your organization has multiple instances of SonarQube, you can now configure all of them in the Settings page or through the public API.Improvements 📈
  • Added type any entity responses in the public API
  • Updated headers for Bird’s Eye report for level-driven Scorecards
ScorecardsCatalogIntegrationsAPISettings & Permissions
Domains in Public API: We’ve released support for domains in the public API. Everything that works for catalog entities will now work for domains.Improvements 📈
  • Added the ability to add, update, and delete configurations for NewRelic and Prometheus to the public API.
  • When editing dependencies through the UI, you can now set descriptions.
  • Improvements to permissions page
Bug fixes 🐛
  • Fixed issue with median scores and levels in the Scorecard stat section
  • Services and resources that are children of a domain are now being properly pulled into a team’s details page
ScorecardsCatalogIntegrationsAPICQL
Scorecard rules and CQL
  • We fixed a bug where jq comparisons for strings were throwing an error related to type issues.
Improvements 📈
  • Users are now redirected to the query page with results after running a query in the Query Builder
  • Optimizations to OpsGenie API calls to avoid rate limits
Bug fixes 🐛
  • Fixed logic around showing last deploy in the service overview page
  • Fixed issue with auto discovery of New Relic dependencies
ScorecardsCatalogAPICQL
Scorecard rules and CQL
  • We fixed a bug where anyMatch and allMatch could not be applied to Lists from jq or custom data.
Improvements 📈
  • Layout improvement for the service, resource, and domain overview pages. You’ll notice that we’ve moved all the metadata to the top of the page and added tabs so you can quickly see the overview, operations, and code & security information.
  • Added endpoint to delete deployments for a given entity to the public API
Bug fixes 🐛
  • Fixed filtering issue for team in the service, resource, and domain catalogs.
CatalogIntegrationsCQL
Improvements 📈
  • Added direct links to our public docs and the CQL Explorer to our main header; simply click on the ? icon and you’ll see the dropdown with these options as well as our support portal.
  • Various domains related improvements such as showing whether an owner is inherited from a domain or not.
  • Added count to tabs in teams page for members, links, services, resources, and domains.
Bug fixes 🐛
  • Datadog services are properly discovered in import services page
  • Improvements around rate limits when discovering cloud SQL database from GCP
  • Fixed Checkmarx URL for project
ScorecardsCatalogIntegrationsCQLGitOps
We’re super excited to release Domains 🎉. Domains (or domain hierarchy) is a hierarchical grouping of services and resources meant to reflect business (or … domain) context. For example, you could represent Cortex’s Scorecards system in the following hierarchy:
Domains can also be used to drive ownership. Instead of defining ownership of services and resources one by one, you can define ownership at the Domain level and have the child services and domains automatically inherit ownership from the parent hierarchy.You can find Domains under the Catalogs dropdown. Domains are full catalog entities, similar to services and resources – they can be scored, have custom data/integrations, owners, be managed through GitOps or UI, etc. Learn more in the docs.
CQL
Improvements 📈
  • Run query button is simplified and always opens modal to allow you easier filtering when running queries
Bug fixes 🐛
  • Fixed occasional page crash when editing resource definition page
  • Fixed an issue with custom CQL queries, allowing them to be used in numeric rules
ScorecardsCatalog
Catalog Header Item: The header navigation was getting long, so we’ve moved all entities such as services, resources, and teams into a single Catalog dropdown in the menu.Improvements 📈
  • Added ownership description to the edit owners form and base path to the repo form to the corresponding edit sections for services and resources
Bug fixes 🐛
  • Fixed issue with adding a level-less bug to a ladder driven Scorecard
  • Added resource definition back into the resource overview page
ScorecardsCatalogIntegrationsAPICQLSettings & Permissions
Azure DevOps support in the Developer Homepage: We’ve added support for Azure DevOps in the Developer Homepage. If you have Azure DevOps set up, you’ll be able to see your open pull requests as well as any reviews you’re assigned to.Scorecard rules and CQL
  • You can use .map, .average, and .average_by on lists in CQL.
  • We’ve made deploys full objects in CQL. You can do things like deploys(lookback=duration("P7D"),types=["DEPLOY"]).filter((deploy) => deploy.customData.leadTime > 100).count <= 5 to query on deploys that match certain custom data values. To see what’s available in the full deploy object, check out the CQL explorer.
  • You can now specify git repos in CQL if the repo you want to check is different from the repo tied to a service. To do so, just pass in the repo identifier, e.g. git("github:org/repositoryName"). You can also combine this with custom data and do things like git("github:" + custom("my-custom-repo")).fileExists("README.md").
Improvements 📈
  • Enhanced CQL explorer search to make it easier to find what you’re looking for.
  • You can now specify your company’s custom sub domain for Datadog in the Settings page if it exists. We’ll use this to generate proper links to Datadog in our service and resource pages.
  • We’ve added the ability to specify groups during the service and resource import flow.
  • You can now specify arbitrarily nested custom data type of any type for deploys – not just key-values.
  • Scorecard response in public API now includes the level name that a rule is associated with.
  • Developer homepage handles fetching pull requests from multiple git providers.
  • In the App Preferences page in settings, admins can toggle auto import for resources.
  • In the Permissions page in settings, admins can specify the default role for new users.
Bug fixes 🐛
  • Fixed inaccurate status info in dependency details of a service or resource page
  • Improved integration guess in rule builder when editing an existing rule that is supported for multiple integrations.
ScorecardsWorkflowsCatalogIntegrationsCQL
Revamped Scaffolder Workflow: Instead of adding and editing service templates in the Settings page for Service Templates, you can now do so directly in the Scaffolder page. Non-admin users won’t see the “Add template” or “Edit” buttons on the page.Scorecard rules and CQL
  • We added gcp.details to CQL, which allows you to access GCP metadata (as seen in the catalog overview pages) as an object in CQL queries, reports, and rules
Improvements 📈
  • Added support to specify Veracode sandboxes in the service or resource YAML
Bug fixes 🐛
  • Fixed issues fetching Veracode findings for applications with spaces in the name
ScorecardsCQL
Improvements 📈
  • Markdown files at the root directory of a repository will now be automatically pulled into the Documents tab of the service or resource it’s tied to.
  • The graph shows level information for Scorecards.
  • Added CQL data type information to CQL Explorer, and deprecated the old CQL Docs tab in favor of the explorer.
  • Visual improvements for the rule modal in the Scorecard create and edit pages
Bug fixes 🐛
  • All teams dropdown in forms shows team name if it exists
ScorecardsCatalogIntegrationsAPICQLInitiatives
Overhauled API docs: We just released our completely overhauled API docs! The new API docs have more detail and include useful details like examples for each API. Let us know your feedback!Initiatives for Resource Scorecards: You can now create Initiatives that target Resource Scorecards!Resource definition public API: Added the ability to get, create, update, and delete resource definitions to the public API.Scorecard rules and CQL
  • We added aws.details to CQL, which allows you to access AWS metadata (as seen in the catalog overview pages) as an object in CQL queries, reports, and rules
  • We’ve updated dependencies.in and dependencies.out to return the dependency object
  • You can now check the number of channels for a given entity using slack.channels.count
Improvements 📈
  • Ability to associate lambda / ecs with an entity based on tags instead of just ARNs
ScorecardsCatalogIntegrationsCQL
Checkmarx Integration: We’ve rolled out our Checkmarx Integration! To set it up, simply add your credentials in the Settings page and add your application names to your YAML files. After doing so, you’ll be able to see your vulnerabilities in the catalog page and write Scorecard rules for the vulnerabilities. Take a look at the docs for more information.CQL Report & Query Builder support for Resources: We’ve added the ability to create CQL reports and run queries from the Query Builder on resources. You can also specify to run a query just on specific resources.Improvements 📈
  • Various performance improvements to how we handle Scorecard re-evaluations and queries run through the Query Builder and CQL reports
  • Added the dependency description to the dependency details row and tooltip
  • Code & security pages for services & resources include Veracode findings and Checkmarx vulnerabilities
Bug fixes 🐛
  • Fixed issues with duplicate owners
ScorecardsCatalogIntegrationsInitiatives
Veracode Integration: We’ve rolled out our Veracode Integration! To set it up, simply add your credentials in the Settings page and add your application names to your YAML files. After doing so, you’ll be able to see your vulnerabilities in the catalog page and write Scorecard rules for the findings. Take a look at the docs for more information.Jira Default JQL: If you’re a Cortex admin, you can now override the default JQL for your Jira integration in the Jira Settings page.Improvements 📈
  • You’ll see a warning popup if you try to delete a rule or level from a Scorecard that would cause the prioritized rules or levels of an Initiative to be empty.
  • You can now use the query builder on both services and resources.
Bug fixes 🐛
  • Scorecard export includes all filters
ScorecardsWorkflowsCatalogIntegrations
Archived teams: We’ve added support for archiving teams. You can archive or unarchive teams by clicking the three … button on the top right of the team page. Archived teams will be hidden from the teams list page by default. To see them, simply toggle “Show archived”.Archived teams will still show up in service and resource owners lists and reports.Overhauled Catalog pages - Overview, Operations and Code & Security Pages: We’ve added two new pages for services and resources:
  • Operations: this page aggregates operational information such as service health, K8s details, deploys, and more.
  • Code & Security: this page aggregates code quality and security information such as code coverage, code smells, vulnerabilities, and more.
Both pages can be found in the side nav of your service or resource.We’ve also updated the homepage for entities to show relevant operations and code & security information.Directory structure for Cookiecutter templates: You can now use Cookiecutter templates that are stored in subdirectories within a repository by specifying an optional field for “Subdirectory for Cookiecutter template” during service template registration.Improvements 📈
  • Updated color scheme for the Bird’s eye and All Scorecards report
  • Added the Snyk issue ID to the issue row
  • Fixed AWS dependency sync timeouts
  • Added name for Prometheus SLOs
Bug fixes 🐛
  • Fixed toggling from “My” to “All” notifications in Settings page
ScorecardsEng IntelligenceIntegrationsCQLSettings & Permissions
GitLab support in the Developer Homepage: We’ve added support for GitLab in the Developer Homepage. If you have GitLab set up, you’ll be able to see your open merge requests as well as any reviews you’re assigned to.Scorecard rules and CQL
  • Support string results for SonarQube metrics in CQL
Improvements 📈
  • We’ve added support for having multiple Git providers configured throughout Cortex. Note that this won’t work for the developer homepage yet
  • AWS integrations, including the Resource Catalog, can use roles from the instance (ECS/EC2) instead of manually provided credentials. Note that if you already have credentials defined in k8s secrets, you’ll need to remove them for the instance credential provider to be used.
  • New “Old” and “Complex PR” badges in the open PRs and assigned reviews tab of the developer homepage
Bug fixes 🐛
  • Fix for Mend vulnerability links if using the legacy URL
  • Various Scorecard bugfixes when adding, updating, or deleting levels or rules
WorkflowsIntegrationsCQL
Azure Devops support in Scaffolder: We’ve added ADO support in the Scaffolder to create new services. To start using the Scaffolder, add templates in the Service Templates settings page.Improvements 📈
  • Visual improvements to the CQL report data
Bug fixes 🐛
  • Fixes to certain cases where previous scores were not being reused when rate limited for GitHub code search and Snyk rules
  • Active query is cleared when it’s done running and will appear in the Recent Queries section
ScorecardsEng IntelligenceCatalogIntegrationsAPIGitOps
Actions Improvements: You can now create a templatized, human readable response message for Actions after they run. These will appear in the response tab of the Actions results. We also updated the historical results to open in a side panel instead of a modal.Lambdas in Service Import: In the Service Import flow, AWS Lambdas will show up in discovered services and can be imported. The arn information for that service will be shown in the service homepage.Bitbucket & Jira OAuth Support: If using Bitbucket or Jira on-prem, you can now integrate using OAuth in the Bitbucket Settings page and / or Jira Settings page by clicking the dropdown on the top right and selecting “On-Prem OAuth”.Improvements 📈
  • The public scorecard descriptor endpoint now accepts a dryRun flag for validating scorecard YAMLs without persisting changes
  • Added APIs to list all Scorecards, get the current level and next steps for a Scorecard for a specific entity, and delete a Scorecard by tag
  • Support for custom keys containing slashes via API
  • Added a toggle to hide teams with 0 members to the hierarchy view
  • Moved graph filters to modal and added ability to filter by resource types
  • Editing a repo for a service is now supported for Bitbucket
  • Progress report in executive report can be filtered by different time ranges
  • We’ve added the integration validation button to the Bugsnag Settings page so that you can validate that your connection is working as expected
Bug fixes 🐛
  • Scorecards rules only support positive point values
  • Switching input types in Actions works as expected
ScorecardsCatalogIntegrationsCQLSettings & Permissions
Scorecard rules and CQL
  • Support for git.top_language in CQL. Note that this will not work for Bitbucket on-prem or Azure DevOps
Improvements 📈
  • Added Bugsnag page to the catalog with errors information for services and resources
  • Ability to duplicate Scorecard rules while creating and editing Scorecards
  • UX improvements for filters in the Progress Report
  • Extended support of Actions parameters to include {{context.initiatedBy.email}}, {{context.initiatedBy.role}}, and {{context.iso8601Timestamp}}
CatalogIntegrationsAPISettings & Permissions
Actions: You can now define custom self-serve Actions, including customizable input fields, that can send payloads from Cortex to any API (internal, external, or webhook). Actions can be tied to entities or can be standalone. Some example actions you can build are:
  • Deploy action that asks the user for target environment and announcement channel, and triggers a build on GitHub for the service
  • Bug file action that creates a correctly formatted JIRA ticket in the right project
  • One-click temporary access token provisioning for devs
  • Automatic AWS resource provisioning
Take a look at our docs & Help Desk guide for more information.Mend SCA Support: We’ve added support for Mend SCA, in addition to our existing Mend SAST support.Improvements 📈
  • OpsGenie support in the developer homepage
  • Expanded the Prometheus integration to support multi tenancy
  • UX improvements for the edit department page.
ScorecardsCatalogIntegrationsCQL
Sumo Logic Integration: You can now map your SLOs from Sumo Logic to services in Cortex and write Scorecard rules on these SLOs. To get started, add your auth credentials in the Settings page.Scorecard rules and CQL
  • We’ve added a cluster lookup option to the k8s.spec rule so that you can check an entity’s specs for a specific deployment cluster.
Improvements 📈
  • UX improvements for the create and edit team page.
ScorecardsCatalogIntegrations
Workday Integration: We just released an integration with Workday! You can use this integration to track service ownership, ensuring accurate ownership as teams change and grow. To set up the integration, you’ll need to generate a report and configure the URL as well as the credentials in the Settings page.Improvements 📈
  • Filtering improvements to the All Scorecards report.
ScorecardsCatalogIntegrationsCQL
All Scorecard’s Report Hierarchy Support: The All Scorecards Report is now Hierarchy-aware. This will make it significantly easier to find the information you’re looking for and aggregating data at every level of your engineering organization. The report lets you traverse your data and aggregate across different dimensions such as teams and groups.YAML Linter: We’ve added a linter tool to help you validate your catalog entity and Scorecard YAMLs. You can toggle between the two types, access the relevant documentation for both, and see any errors in your YAML. You can access the linter in the tools dropdown in the main header.Scorecard rules and CQL
  • The git.numRequiredApprovals rule is now supported for Azure DevOps.
Improvements 📈
  • Completely overhauled service and resource import flows to make it more intuitive.
  • UX improvements for the Edit Hierarchy page.
ScorecardsCatalogIntegrationsCQL
GitHub Advanced Security: We’ve added support for GitHub Advanced Security as a source for vulnerabilities. In order to see code scanning alerts from GitHub Advanced Security, they must be defined as a source. For example git.vulnerabilities(severity=[], source=["GITHUB_ADVANCED_SECURITY"]) < 2 .If you want to see vulnerabilities from both GitHub Advanced Security and GitHub Security Advisory (where our current vulnerabilities are sourced from), you’ll need to specify both as sources. For example git.vulnerabilities(severity=[], source=["GITHUB_ADVANCED_SECURITY", "GITHUB_SECURITY_ADVISORY"]) < 2Improvements 📈
  • We’ve added support for pub/sub resources from GCP.
  • Service page shows the last time the service was updated.
  • Service scorecard page shows the time scores were last evaluated.
  • CQL report shows the time of last evaluation. To refresh a report, click the … button in the top right.
  • Updated our auto-import flag to import GCP resources on a cron in addition to AWS resources. If interested in testing this flag, reach out to our team and we can enable this on your workspace. The flag ensures that your resource catalog always stays up to date with the resources we discover in your cloud provider.
  • UX improvements for the Sentry integration in the catalog
Bug fixes 🐛
  • Resolved incidents are no longer displayed in the active incidents section for a service.
  • Fixed dependency links for resources.
ScorecardsCatalogIntegrationsAPI
Improvements 📈
  • In the dependencies page for a specific service or resource, you can now see the incidents and monitors for each dependency. Hovering over the row will show the full information for the dependency, including the endpoints and metadata.
  • We’ve added support for cloud load balancing resources from GCP.
  • We’ve extended Datadog region support to include US3, US5, and US1_FED in addition to US1 and EU1
Bug fixes 🐛
  • Progress bar shows correct progress
  • Deleting a rule during Scorecard creation when starting from a template works as expected
ScorecardsCatalogIntegrationsCQL
New Resource Types: We’ve added support for importing DynamoDB and ELB resources. Simply click the “Import Resource” button and we’ll include these resources in the discovered resources list.Create & Edit Resource Definitions UI**:** We just released updated pages for creating and editing resource definitions that match the create & edit Scorecard page experience. The updated page retains all of the same options but is all on one page and hopefully easier to use!Scorecard rules and CQL
  • The git.hasCortexYaml() rule is now supported for Azure DevOps.
Improvements 📈
  • We’ve added a toggle in the Developer Homepage to filter out reviews that are assigned to a team you’re part of but not assigned to you directly.
  • We’ve added the ENABLE_RESOURCES_AUTO_IMPORT flag to auto import AWS resources on a schedule instead of manually importing them through the UI.
  • We’ve added the integration validation button to the Rollbar Settings page so that you can validate that your connection is working as expected
ScorecardsCatalogIntegrationsInitiatives
Revamped Create & Edit Initiatives UI: We just released updated create and edit Initiative pages that match the Create & Edit Scorecard pages. The updated pages retain all of the same options but is hopefully easier to use!Improvements 📈
  • Added the mapping key (such as the repo) from the related integration in the import service list
  • Updated edit query page
Bug fixes 🐛
  • Deleting a resource definition correctly deletes corresponding resources
Last modified on November 18, 2026