Skip to main content
Updates released in Cortex in 2022, newest first.
ScorecardsCatalogIntegrationsCQL
Google Cloud support for the Resource Catalog: We’ve released support for importing Cloud Functions, Cloud SQL, and Cloud Storage resources from GCP. To get started importing resources, make sure that you have Google set up as an integration and click the “Import Resources” button on the top right of the Resource Catalog.Scorecard Rule Exemptions: If you have a service or resource for which a Scorecard rule doesn’t apply to, you can now request an exemption for that rule by clicking the … button on the right hand side of any failing rule. You can request a temporary or permanent exemption, which has to be approved by an admin. Read more about rule exemptions in our guide.Scorecard rules and CQL
  • Rollbar RQL queries now return full result sets, regardless of type. Previously we would just process numerical outputs, but now we will return back out the full list of rows/columns, or null if the result set is empty.
ScorecardsWorkflowsEng IntelligenceCatalogIntegrationsCQL
Revamped Scaffolder UI: We just released a new Scaffolder experience that matches the Create & Scorecard page experience. The updated Scaffolder retains all of the same options but is all on one page and hopefully easier to use!Continued Service Catalog Improvements: We’ve added live error rate and apdex columns to the service catalog, from New Relic. Additionally, you can now see repository and on-call information for a specific service by hovering over it.Scorecard rules and CQL
  • We’ve added GitLab support for our code search rule. You can now find all instances of code search query from within a GitLab repository. You can also filter by path, filename, or extension. For example, “git.code_search(query = “icon”, file_extension = “css”)”
  • You can query metadata for a specific entity such as entity_name, entity_created, and entity_last_updated. For example, you can write queries to ensure standard naming across services in certain groups or owned by certain teams using entity_name.
Improvements 📈
  • Updated filter button & modal in the Executive Report
  • We’ve added the integration validation button to the Opsgenie Settings page so that you can validate that your configuration is working as expected
ScorecardsWorkflowsCatalogIntegrationsAPISettings & Permissions
SonarQube entity page improvements: We’re now pulling quality, maintainability, and security information from SonarQube in the service and resource pages to make them more useful for you. If you’re using SonarQube but don’t have it set up in Cortex yet, take a look at our docs to get set up.Improvements 📈
  • Show Snyk organization/project names where applicable (instead of uuids)
  • We’ve added the integration validation button to the Snyk Settings page so that you can validate that your configuration is working as expected
  • Made minor visual adjustments to the Scorecard Details page, including moving the filter button to a location that better reflects what the filter acts on
  • Improved the display of the active incident lists for a service or resource at smaller display widths
  • Improved identity mapping logic to encompass a few more cases where we can auto-associate owners of services based on data from integrations
Bug fixes 🐛
  • Improved the loading state of the Scaffolder and provides a more accurate indicator when the work is complete
  • Ceased showing catalog column headers if there are no results
  • Skip retries when receiving 404s from third-party integrations
  • Gracefully handle a failed scorecard ingestion by continuing to attempt to process all other scorecard YAML files that may be in the changeset
  • GitHub configuration validation will now run against the configured host, if provided, instead of always using GitHub’s cloud API
  • Fixed importing services from Azure DevOps due to a response shape change
  • Gracefully fail fetching SonarQube information for a service that has no associated SonarQube project
ScorecardsWorkflowsCatalogIntegrationsAPICQLSettings & Permissions
Scorecard rules and CQL
  • Added a new rule to list out all git branches, including the ability to filter the branches. See examples and more in the documentation.
Improvements 📈
  • Added support for multiple Prometheus accounts
  • Added support for multiple New Relic accounts
  • Added support for relative OpenAPI links outside of a service’s repository
  • Added active incident and monitor status information for all services on the list page (previously only showed up for “my” services)
  • Improved the efficiency of processing Bitbucket webhooks by only parsing changed files instead of doing a full repo scan
Bug fixes 🐛
  • Fixed an issue with the scaffolder failing when invoked on an entity with dependencies
  • Fixed an issue where invalid configuration for PagerDuty and Datadog caused large amounts of alerts to appear on the service catalog page
  • Fixed an issue when using the scorecard API causing unnecessary writes, which could trigger 403s for tokens with insufficient (e.g. read-only) permissions
  • Fixed an issue with SonarQube configurations that used a forward slash in the host
CatalogIntegrations
Improvements 📈
  • Added the ability to force refresh active incident and monitor status for services in the list view
  • Added clarification for supported JQ operations in docs
  • Improved error messaging when attempting to edit a service or resource YAML file with invalid YAML
Bug fixes 🐛
  • Fixed a scenario where active incident status did not show up on a service or resource homepage on first page visit
  • Fixed an issue where Dynatrace was not properly showing up as an installed integration
ScorecardsWorkflowsCatalogIntegrationsCQL
New features ✨
  • CQL Reports: Cortex users can now generate reports based on queries, gaining more visibility into services and resources than ever before. Dive beyond Booleans and see the actual values CQL provides by using one of the templates provided or starting a report from scratch yourself!
  • Service catalog overhaul: Cortex now puts even more power at your fingertips by pulling incident management information directly into the service catalog. When viewing the My Services tab, Cortex now highlights any active incidents and failing monitors associated with services inline, saving you time and clicks. This works with Datadog and PagerDuty.
Improvements 📈
  • Added ability to validate the GitLab integration
  • Visual improvements to the Scorecard Details page
  • Reduced the width of the side nav at small viewports to increase the amount of real estate available for the main content
  • Added a refresh button for GitHub and GitLab in the scaffolder flow so you don’t have to break your rhythm to get the most up-to-date info.
Bug fixes 🐛
  • No longer using invalid git refs when evaluating git-related rules
  • Fixed horizontal scrolling and the fixed table header on the Heatmap report page
  • Fixed Resource Definition editor height — you can now see the content again! 🙈
  • Fixed an edge case causing the graph page to crash when an entity lookup failed
  • Fixed an edge case in keyboard usage of site search, causing a JavaScript error and potential confusion
ScorecardsCatalogIntegrations
New Create & Edit Scorecard Pages: We’ve learned a lot over the past few years about how our users use Cortex, and we’re incorporating all of these learnings into a simpler and more intuitive set of flows without sacrificing any of the power and flexibility that Cortex provides today. You’ll notice a new Scorecard editor that retains all of the same options but is all on one page and easier to use!Improvements 📈
  • We added support for automatically importing Kafka clusters from AWS. To take advantage of this new feature, make sure to update the IAM policy you’re using with Cortex to include kafka:List* and kafka:Describe* (as noted in the updated documentation). Once that’s done, Kafka clusters will show up in the Resource discovery, just like S3 and RDS do today.
ScorecardsWorkflowsCatalogIntegrationsInitiatives
JIRA Issues Help Desk Guide: We’ve added a Help Desk article about creating Jira issues based on Initiatives.Improvements 📈
  • Made the page layout more responsive, particularly at larger viewports
  • Added cron job support for k8s agent
  • Prevent re-evaluating scorecards when editing metadata, reducing extra calls to third-parties (such as git providers)
  • Scaffolder: Minor improvements for advanced users of the scaffolder:
    • @cortex_inputs is being transitioned to _@cortex_inputs
    • Users can now properly template other fields in the cookiecutter.json file using the _@cortex_inputs variable
    • Values for @cortex_inputs (now _@cortex_inputs) in the cookiecutter.json file, usually left there for testing templates, are correctly overridden when the template is executed through Cortex.
Bug fixes 🐛
  • When adding and editing links via the UI, we now correctly allow relative paths (in addition to fully-qualified URLs) for OpenAPI and AsyncAPI link types.
  • The logic for importing a service that tracks a Kubernetes resource was previously only working for Deployments. We have now fixed it so that newly imported k8s services should behave more accurately across our other resource types (stateful sets, argo rollouts, and cron jobs).
ScorecardsCatalogIntegrationsInitiatives
JIRA Issues: You can now create issues in JIRA from Initiatives. To do so, make sure that JIRA is set up and click the “Create Issue” button in the new “Issues” tab in the Initiative Details page. The issues take a few minutes to create so you won’t see them instantly but they’ll be in the “Failing” and “Passing” tabs next to their corresponding service.Mend Integration: We’ve rolled out our Mend Integration! To set it up, simply add your credentials in the Settings page. We’ll auto-guess based on the repo name for a service but you can override the application ID in the YAML file. After setting this up, 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.Improvements 📈
  • We’ve added the integration validation button to the Dynatrace Settings page so that you can validate that your configuration is working as expected.
Bug fixes 🐛
  • Fixed page crashing issue if someone visited the All Scorecards report page after looking at the Heatmap report.
ScorecardsCatalogIntegrations
New Support Portal: You’ll notice that the the help desk has been migrated to a brand new support portal experience! You can find all the same information it contained earlier, as well as a new set of FAQs, guides, as well as an easy way to reach out to our support team.Improvements 📈
  • If a service has a base path, we now show it in the “git” section of the service
  • Large JSON payloads for custom data are now displayed in a modal and collapsed by default
  • Support for a default JQL query for Jira issues in the catalog. By default we check for issues with status Open or To Do, but for Jira instances with custom issue types, you can now specify per service what issues you care to see in the catalog.
Bug fixes 🐛
  • Increased size for Grafana embeds
  • When looking at the Scorecard information for a specific service, you can see the value that was computed for that rule by hovering over the row.
CatalogSettings & Permissions
Improvements 📈
  • Clicking “Configure Service” on the Service or Resource YAML page will open the YAML editor instead of the UI editor. The “Configure Service” is only displayed if UI editing is enabled.
Bug fixes 🐛
  • Fixed a permissions bug and now anyone with permission to edit services and import new resources.
ScorecardsWorkflowsCatalogIntegrations
Panel for Service Details in Scorecard: In the Scorecard page, clicking on a service will open a side panel with all the details for that specific service.GitLab Pipeline configuration in Scaffolder: The scaffolder allows you to enable Gitlab pipelines on new repos that are created during the flow. You’re also able to set variables for the pipeline, making it even more of a seamless experience for developers.Clearing K8s Clusters: In the K8s settings page, you can now clear all cached data sent to Cortex from one of the agents you’ve deployed.Improvements 📈
  • We heard your feedback loud & clear, the pills were aggressively clamping important information. We’ve fixed this so that the full name of the team or group is displayed in the homepage without needing to hover on the pill itself.
  • The linter tab in a resource definition now shows the schema as well as an example for the YAML so that you have a clear starting point and can see what’s required.
  • Headers in the reports tables now clamp to three lines instead of one to make it easier to read more of the rule.
WorkflowsCatalogIntegrationsGitOps
AWS Resource Dependencies: If you have AWS configured, Cortex can map dependencies between your services and resources with specific AWS tags.
  • Cortex will automatically create dependencies between a service and any resource where the AWS entity is tagged with key = “service” and tag value = the service’s x-cortex- tag. You can customize the tag key we use, in the AWS integration settings, or leave it blank to use “service” as the key.
  • You can also explicitly specify AWS tag keys and values in your service’s cortex.yaml file, and Cortex will create dependencies between that service and any resource whose AWS tags match at least one of the specified tags. See our docs page for more details.
Improvements 📈
  • We added the ability to configure whether pipelines are enabled for new GitLab services you make using the Scaffolder
ScorecardsCatalogIntegrations
Edit Service & Resource Page: We’ve revamped both these pages to make the editing process easier. As part of this, we’ve moved editing YAML under the “Configure Service/Resource” option so that all editing is unified under one page.Improvements 📈
  • We’ve now enabled much faster evaluations for scorecard rules across all your services by distributing them evenly throughout the day!
  • Clicking on a Scorecard from a teams page will auto apply that team as a filter in the scores table
  • Long descriptions for custom data items are expandable
  • Updated the description in the Kubernetes Settings page
Bug fixes 🐛
  • Timeline row icons are consistent in size
  • Undefined error when grouping action items by entities is now fixed
ScorecardsCatalogIntegrationsCQLGitOpsInitiatives
Action Items: We’ve added “My Action Items” to the main header. This is a personalized experience for developers that combines initiatives + failing scorecard rules across all their services in one place to streamline their work in Cortex.The “My Action Items” tab in the Initiatives page will be deprecated in the coming weeks.Scorecard rules and CQL
  • git.code_search can be used without specifying the query parameter. For example, you can now issue git.code_search(path = “/path/to/file.json”) instead of git.code_search(query = "", path = “/path/to/file.json”).
Improvements 📈
  • In the resource homepage, we’re hiding sections that have no data.
  • Performance fixes for the Resource import flow
  • Automatic dependency linking between resources and services using tags (if the resource in AWS has a tag of service: service’s-x-cortex-tag, it’ll automatically link the two
Bug fixes 🐛
  • In the All Scorecards report, when grouping by team, the link to the team’s page is fixed.
ScorecardsCatalogIntegrationsCQLGitOps
Keyboard shortcuts for Search Modal: You can now open the search modal with cmd + K and navigate the results using your arrow keys. To go directly to the object, hit enter.Scorecard rules and CQL
  • New entity_descriptor built-in CQL variable which provides the entity’s underlying catalog descriptor YAML as a JSON blob, which allows you to write any arbitrary rules on your entity metadata.
Improvements 📈
  • Further improvements to background task throughput, so that Scorecards and queries run faster
Bug fixes 🐛
  • Fixed serialization bug in Datadog SLOs
  • Fixed bug in Nuget package parsing, which caused the parser to incorrectly handle empty item groups
CatalogAPIInitiatives
Group Subscription: If you don’t own any resources directly but want to see them under “My Resources”, you can “subscribe” to groups under Settings → User Preferences. The same works for services as well!Nuget Lockfile Parsing: We now automatically parse nuget lockfiles from your git repositories, and exposed an endpoint to parse csproj files automatically!Improvements 📈
  • Too many to list this week! We’ve been making lots of changes to the new design based on your feedback. Still seeing an issue with the redesign? Let us know!
  • We overhauled our notifications for Initiatives, making them more relevant, easy to understand, and actionable.
We just released our long-awaited redesign 🎉
  • Bringing a modern look-and-feel to Cortex
  • Improving readability
  • Better layout of information to put most important information first
  • Making better use of larger screens
  • More visual consistency across different pages to make it easier to use
We’re super excited to hear your feedback – let us know if there’s anything that we can improve and how we can make the design better for you
ScorecardsIntegrations
Bug fixes 🐛
  • Fixed a race condition when updating Scorecard filters where the updated filter wasn’t being applied in time.
Improvements 📈
  • As your service graph evolves in Dynatrace, we’ll automatically sync those dependencies over to Cortex.
  • We’ve significantly upsized our infrastructure, and background tasks like Scorecard and Query Builder evaluations are running 2.5x faster.
ScorecardsCatalogInitiatives
We’ve released Scorecards for Resources! Similar to services, you can now track resource quality and verify things like “Do all infrastructure assets have owners?” and “does every RDS instance have multiple availability zones?”. To get started, create a Scorecard from scratch and toggle the Category from Services to Resources. The rest of the flow is unchanged. When creating a scorecard for Resources, you can also filter by resource type, in addition to specific groups. All Scorecard related Help Desk articles have been updated to reflect these changes.Note: Resource Scorecards are supported in Reports, but they are not supported for initiatives yet.
ScorecardsIntegrationsAPICQL
Scorecard rules and CQL
  • We just released support for GitHub Dependabot issues in CQL! Can see documentation here, but you can now write rules like git.vulnerabilities(severity=["CRITICAL", "HIGH"]) = 0
  • Support for multiple Kubernetes clusters for label matching rules.
Bug fixes 🐛
  • Fix for support S3 details for multiple AWS accounts in the Catalog
  • Fix to disallow duplicate scorecard rules within a single scorecard
  • Fix for bulk upload for teams in the public API to make the operation fully transactional
ScorecardsCatalogIntegrations
Dynatrace: We now have support for Dynatrace! With the integration, you’ll get automatic service discovery along with dependencies, as well as support for SLOs in both the catalog and Scorecard rules.Support Email: If you can’t find what you’re looking for, feel free to email our support team at help@cortex.io. We’ve added a banner to the Help Desk with this information as well.Scorecards as Code: As mentioned in last week’s announcement, you can now manage your Scorecards through git. We’ve added an article to the Help Desk to walk you through the setup process.Improvements 📈
  • The app now surfaces Request IDs with errors! With every error that is surfaced on any page now, you would also see a Request ID that you can share with the Cortex team! This makes it easier for everyone to find the underlying issue 🙂
ScorecardsWorkflowsGitOps
Scorecards as Code: You can now manage your scorecards through git, just like the rest of your catalog. Read all about it in our docs.Export Scorecards to YAML: To transition a Scorecards to the GitOps workflow, you can now easily export a Scorecard to its YAML representation under the “more actions” dropdown when viewing a Scorecard.
WorkflowsCatalogIntegrationsAPIGitOps
Multiple AWS Accounts: We now support multiple AWS accounts. To get setup with AWS, go to the Settings page and add as many accounts as your team has or your heart desires. We use AWS for ECS service discovery and resource discovery of type S3 & RDS.API Documentation: We now support the ability to upload API documentation via our public API! Read more in the docs: https://docs.cortex.io/docs/reference/basics/external-docs#upload-via-apiAzure DevOps Webhooks: We now support out-of-the-box Gitops workflow for Azure DevOps. Read more about getting set up in the docs: https://docs.cortex.io/docs/setup/gitops#azure-devopsImprovements 📈
  • Snyk issues in the Catalog link to the actual project issue instead of the issue writeup
CatalogIntegrations
K8s Definition Viewer: In the K8s tab for a service or resource, you can now view its definition by clicking the “View Definition” button on the right hand side.Bug fixes 🐛
  • Dependencies have the right icons corresponding to its resource type. If you hover over the icon, you’ll see a tooltip with the tag for that type.
ScorecardsCatalogIntegrationsAPICQL
Export Discovery Audit: We’ve added an “Export” button on the top right of the Discovery Audit page to export the full report to CSV. It includes the report name, type, source, and whether it’s been ignore or not.Scorecard rules and CQL
  • The git.branch_protection rule now works for GitLab in addition to GitHub.
  • The git.fileContents rule now works for Azure in addition to GitHub, GitLab, and Bitbucket.
Improvements 📈
  • We’ve added the integration validation button to the Datadog Settings page so that you can validate that your configuration is working as expected.
  • Sentry events in the timeline link to Sentry.
  • There’s a couple new resource definition icon options.
Bug fixes 🐛
  • Metadata for dependencies is properly displayed in the UI. We’ve also added badges to make it clear where the dependency is coming from - YAML, API, or APM.
ScorecardsCatalogIntegrationsInitiatives
Ladder Driven UI for Scorecards: If you’re using ladders for your Scorecard, it can be a confusing experience for developers with the percent indicators and the ladder badges. To clean up this UX, we tweaked the visuals when you have a ladder enabled to present more of a “progress indicator” rather than a percent indicator.Descriptions for Owners: In the service YAML, you can now specify descriptions for owners. You can also specify whether notifications are enabled for Slack channels.Improvements 📈
  • We’ve added the integration validation button to the Pagerduty Settings page so that you can validate that your configuration is working as expected.
Bug fixes 🐛
  • Initiatives due dates are now inclusive of the date
ScorecardsIntegrations
Improvements 📈
  • We’ve added the integration validation button to the Slack Settings page so that you can validate that your configuration is working as expected.
  • Scorecard templates have failure messages linking to relevant documentation.
  • Improved performance on service YAML processing
Bug fixes 🐛
  • Fix visual issue for descriptions in Settings pages.
  • Progress report share links and copying the data properly handle filters.
ScorecardsCatalogIntegrationsAPIGitOps
Improvements 📈
  • Added x-cortex-definition validation in the YAML linter for Resources (through our public API or through our GitHub app on PR checks)
  • Resources with invalid resource definition schemas show a warning banner highlighting if the resource you’re viewing is out of compliance with the resource definition
  • If you specify dependencies during the Scaffolding process, you can now access them in Cortex Inputs.
  • You can now filter the dependency graph by groups even if you have a service or resource selected.
  • Bird’s eye report has a toggle to show teams with 0 services when you group by teams and enable the Team Hierarchy.
  • K8s details in the service and resource pages now show all information in order of last updated. To find a specific container or type, you can use the filters on the left hand side.
Bug fixes 🐛
  • Retain saved queries longer than 30 days
ScorecardsEng IntelligenceCatalogIntegrationsAPICQLGitOps
Manually Import Resources: You can now manually create resources based on your custom Resource Definitions through the UI instead of having to use the API. To get started, click “Import new resource” in the Resource Catalog, and then select “Create a resource manually”.Scorecard Templates: When creating a new Scorecard, you’ll now be able to choose from a set of Scorecard templates, such as DORA metrics or service maturity. You’ll be able to change the metadata for this Scorecard at any time, as well as the rules and levels.JIRA Details: If you’re using JIRA, you can now view any tickets related to your service or resource in the Catalog page under the “JIRA Tickets” tab.Scorecard rules and CQL
  • Azure DevOps support for existing Scorecard rules: You can now use the Check if file exists in Git and Check if Git file contents match a regular expression rules if you’re using AzureDevOps, just make sure that you have the integration configured in the Settings page & your service’s YAML has a x-cortex-git entry with a corresponding azure entry as well
Bug fixes 🐛
  • Groups in Service homepage link to Service catalog instead of Resource catalog
  • Report Card uses rule titles if they exist
  • Retain saved queries longer than 30 days
ScorecardsWorkflowsCatalogIntegrationsAPICQL
Catalog API: We’ve released the unified Catalog API that lets you access Resource entities the same way you would access Services, enabling programmatic use of the Resource Catalog!Scorecard rules and CQL
  • You can use git.branch_protection("branch") to check whether a certain branch is protected in your repository. If you don’t specify the branch, we’ll just use the default.
Improvements 📈
  • During the import service and resources flow as well as the service creation flow in the Scaffolder, you can specify existing dependencies.
  • We’ve added the integration validation button to the Google Settings page so that you can validate that your configuration is working as expected.
ScorecardsCatalogIntegrationsCQL
NewRelic Details: If you’re using NewRelic, you can now see details, such as response time and error rate, in the Catalog page for a service under the “NewRelic” tab.Scorecard rules and CQLImprovements 📈
  • We’ve added the integration validation button to the Okta Settings page so that you can validate that your configuration is working as expected.
  • Icons for resource definitions are now split into sections, making it easier to select the icon that makes the most sense for you.
  • Bird’s eye report shows empty rows when using hierarchy if team doesn’t have any services.
ScorecardsCatalogIntegrationsCQL
Sonarqube Measures: If you’re using Sonarqube, you’ll now be able to see the measures, including code coverage, code smells, and lines of code in the Catalog page for a service, under the “Sonarqube” tab.Git Releases: In the Git page for a service, we’ve added a new section for releases. These also show up in the timeline.Snyk Filtering: We’ve updated the Snyk tab in the Catalog to enable filtering Snyk issues by type (vulnerability, configuration, or license), and have increased the granularity of the fixability of Snyk issues — now you’ll be able to differentiate between issues that are auto-fixable, manually fixable, or not fixable at the moment.Scorecard rules and CQL
  • We now coerce XML contents into JSON for jq, letting you parse XML files in your repository, for example jq(git.fileContents("pom.xml"), ".project.packaging") != null
  • We now have support for optional chaining of Objects, similar to Typescript, or Kotlin. If you run an expression like custom("key").key1?.key2?.key3 = null you can safely traverse null values without an exception being raised.
    • Note: this is a breaking change to our existing behavior. Previously we implicitly allowed optional chaining with . so a similar expression custom("key").key1.key2.key3 = null would work the same way. Now trying to dereference a null value will result in an error.
Improvements 📈
  • Icon picker for resource definitions shows which icon is already selected, if any.
ScorecardsCatalogIntegrations
Prometheus Integration: We’ve rolled out our Prometheus Integration! To set it up, simply add your credentials in the Settings page. Services can now define SLOs (using total and error PromQL queries) in their YAML files. You can also write Scorecard rules on SLOs!Graph Page Filters Revamp: We’ve cleaned up the filters on the Graph page, making it easier to find the dependencies you want.Improvements 📈
  • Service groups have been renamed to groups throughout the app
Bug fixes 🐛
  • Heatmap report can handle duplicate rules
ScorecardsIntegrationsCQL
Scorecard rules and CQL
  • Added support for more powerful code search for GitHub that lets you check things like “are there any *.lock files in the repository that contain ‘abc’?”
ScorecardsIntegrations
Improvements 📈
  • When scaffolding new services with Bitbucket, you now have the option to select which project you’d like to create the new repository within.
  • We’ve revamped the edit levels UI when you’re creating or updating Scorecards.
  • You can now specify the host if you’re using a self-managed Sentry to set up the integration in the Sentry settings page.
  • You can now specify the host if you’re using a self-managed Azure Devops to set up the integration in the Azure settings page.
API
Async API Explorer Support: You can now embed AsyncAPI specs in the catalog. Just create a new link of type ASYNC_API and we’ll render the AsyncAPI explorer.Improvements 📈
  • We now have a proper 404 page if you navigate to a URL that does not exist.
Bug fixes 🐛
  • Fixed issue where icons where unclickable if there was only one item in the Discovery Audit
Settings & Permissions
Improvements 📈
  • We properly display “no permissions” information for users who can’t edit a Settings Page instead of showing a blank page.
Bug fixes 🐛
  • Code lines properly wrap in markdown instead of going off the screen
  • Service page header issues when UI editing is disabled
ScorecardsEng IntelligenceCatalogIntegrationsCQLGitOps
CQL Explorer: In case you missed our update last Thursday, we’re mentioning it again in these product updates. We just released our new CQL Data Explorer to make CQL more intuitive and easier to use! You’ll find it when writing Scorecard rules using CQL or in the Help Desk. The CQL Explorer is an easy to use guide for the data available in CQL, complete with type definitions and ready-to-use examples.Improvements 📈
  • Dashboard embeds no longer need a type – this field is now nullable.
  • Small UI consistency updates, including an improved scrollbar and button sizes when displayed next to input fields.
  • We now parse cortex.yaml files from repos in certain intermediate states, for example, importing a service that has a cortex.yaml when GitOps is enabled.
Bug fixes 🐛
  • Importing event from Discovery Audit would crash in some instances
  • Fix icons in main header bouncing at small viewports
  • Only show “Validate configuration” button if using the Personal Token for Github.
ScorecardsIntegrationsAPI
Delete Deploys API: You can now delete service deployments that match specific filters through our API.Edit Query: We’ve added the ability to edit a query after it’s been saved. After you click the “Edit Query” button, you’ll be able to update the name, description, whether it’s public or not, and the query itself. If you’re using any integrations, you’ll still see the modal to confirm that you want to save and run it.Zendesk Chat: We’ve moved over from using Intercom to using Zendesk chat. Feel free to shoot us any questions you have as you’re using Cortex and our support team will get back to you as soon as they can!Improvements 📈
  • We’ve added the integration validation button to the Github and Sonarqube Settings pages so that you can validate that your configuration is working as expected.
  • When editing fields that support markdown, you’ll now be able to click the “Preview” tab to make sure that your input is showing up as expected.
  • All Scorecards Report has been updated to have the header and first column frozen as you scroll around the table.
  • When adding existing teams to the Hierarchy, you can now select multiple teams at once.
ScorecardsIntegrationsCQLSettings & Permissions
Scorecard rules and CQL
  • Support for JQ expressions for List types. For example, if you have custom data like: [{ "a": 4 }, { "a": 5 }], you can write a rule like jq(custom("data"), "[.[] | .a] | add") = 9
  • Support for New Relic NRQL queries
Improvements 📈
  • Back button now goes back to the list page for that object and is clearly labeled to avoid confusion.
  • K8s Settings page properly specifies the API key role that it needs.
  • Added visualizing dependencies deep dive to the Help Desk.
Bug fixes 🐛
  • Digging into services in levels properly works in the Bird’s Eye report.
  • Remove button in the Github configuration in the Settings page works as expected.
ScorecardsIntegrationsAPISettings & Permissions
Integration Token Validation: After you connect your JIRA instance in Settings → JIRA, you’ll now see a “Test Configuration” button. If everything is set up properly, you’ll see a message confirming that your configuration is valid, or the relevant error otherwise. We’ll slowly be rolling this out to more integrations to make it easier to verify whether your configuration is working, without having to write scorecard rules or use the catalog to test the connection.Delete API for Teams & Departments: We’ve added support for deleting a team or department to our public API.Improvements 📈
  • Direct links to Help Desk articles for Permissions and API Key deep dive articles directly from their Settings pages.
  • K8s Settings page specifics the API role required.
Bug fixes 🐛
  • Onboarding page crash fix after adding multiple services
ScorecardsWorkflowsCatalogIntegrationsGitOpsSettings & Permissions
Edit Team Hierarchies: You can now edit hierarchies directly in the UI! To do so, simply go to the Hierarchy tab in the Teams library and hit edit. You’ll see the ability to create new departments or add existing teams to levels to more accurately model your organization. All departments show up in the Teams library as well and if you click on one of them, you’ll see the department information as well as the teams that are part of that department. You can update the department information or add members to the department by clicking the edit button on the top right. For more details on how to use the Team Hierarchy editor, take a look at our Team Hierarchy Editor help desk deep dive!JIRA Projects in Cortex.yaml: We’ve added support for JIRA projects as a way to map services to tickets, and we automatically “guess” the service name as a project label.Help Desk Guides: You’ll now see deep dive articles for permissioning, API keys, and using the Bird’s Eye report.Improvements 📈
  • Template metadata is now included in the Cortex Inputs after the Scaffolder is used.
  • Linter properly enforces service name and service tag length restrictions.
  • Import service UI improvements such as getting rid of the horizontal scroll.
Bug fixes 🐛
  • Help Desk articles don’t get stuck while loading
  • Dropdowns don’t get lost behind modals
ScorecardsEng IntelligenceCatalogIntegrationsAPIGitOpsInitiativesSettings & Permissions
Breaking Change Notifications: In the Settings Page, you’ll see a new tab for notifications. This is where you’ll see any breaking API change notifications if your workspace has OpenAPI breaking change notifications enabled. You can toggle between seeing just the ones that apply to you, or seeing all the notifications for your organization.Teams Filters in Executive Report: You can now filter the executive report to specific teams to see their specific information for services, deploys, and scorecards.Improvements 📈
  • Dependency management lockfiles are parsed immediately when a service is imported into Cortex
  • Initiatives and actions items performance improvements
  • Tokens and secrets are now masked for a few integrations.
  • The Help Desk documents show a loader while the document is being fetched.
  • K8s settings page shows “Unnamed Cluster” if the name is undefined.
Bug fixes 🐛
  • Automatically mapping projects in Sentry to services in Cortex if the x-cortex-tag matches.
  • Delete user or group modal properly shows the name of the user or group being deleted.
  • A “Forbidden” screen is properly displayed if a user doesn’t have permissions to access the create or edit screen for a specific object instead of showing a blank/broken UX.
ScorecardsCatalogIntegrationsAPICQLSettings & Permissions
Team Hierarchies: We’ve released our Team Hierarchies API that let you model your org structure directly in Cortex, reusing the teams you’ve already added. You can now create “Departments” to group teams together, or even nest teams within teams for reporting purposes. Find the Hierarchy API here.Reports Overhaul: The Bird’s Eye report is also now Hierarchy-aware. We’re super excited for this report and how much easier it’s going to make finding 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, Levels, Service Groups, etc, making it easy for anyone to answer questions like “How many of the Infra Team’s tier-0 services are in the silver Level and why?”. Our CTO, Ganesh, recorded a quick loom on the new reporting and how it works hand-in-hand with team hierarchies! Let us know if you have any feedback, questions, or comments.Service Groups API: We’ve added a new API for tagging services with Service Groups. You’re no longer limited to adding service groups via YAML! You can now use our API to programmatically define service group tags as well.User API Key: New API Key roles that are equivalent to the list of roles available for users. This means you can create keys with a User scope, for example, that can be used to update custom data but not take any admin actions.Scorecard rules and CQL
  • Support to check for dependency on a specific service using depends_on("service-tag")
Improvements 📈
  • Team Tags (identifiers) now support special characters including /s
  • Increase session timeout to 7 days
  • Handle large files from GitHub using blob API
Bug fixes 🐛
  • Resolved bug that incorrectly mapped snyk projects to services in some cases
  • Fix infinite loop on GH App installation
IntegrationsCQL
📚 CQL Docs Table of Contents: We’ve added a table of contents to the CQL docs so that you can click directly to the section you’re looking for. You can also share specific sections with your team simple by clicking on the header of the section and copying the URL.🔻Single Service Filter in Query Builder: In the query builder, you’ll notice a new arrow to the right of the “Run Query” button. If you click it, you’ll be able to run the query on a specific services. This is particularly useful if you’re testing out a new query and want to verify that it works.🕷️ Cluster Info in K8s Settings Page: In the K8s settings page, you’ll see all your clusters along with the timestamp of when they were last updated.
ScorecardsWorkflowsIntegrationsCQLSettings & Permissions
❌  Deleting Cortex Users: We’ve added the ability to remove inactive users from your workspace. Although inactive users wouldn’t have access, they’d still show up under Permissions. Any reference to that user will still work – the user’s name will just show up as “First Last (Deactivated)”.🍪  Cookiecutter Default Values: If you want to use default values in the Scaffolder instead of requiring the input to be filled out each time, you can add use_default: true to the input. You can find an example in our docs.Scorecard rules
  • Snyk: We’ve added support for the Snyk exploitMaturity field, along with better Snyk issue filtering support in CQL to speed up rule evaluation time such as snyk.issues.filter((issue) => issue.exploitMaturity = "MATURE").count < 5
  • You can now use .length for objects in CQL. For example, if you have custom data vulnerability-count that looks like:
    You can now count the number of JSON keys using custom(“vulnerability-count”).length = 2
ScorecardsCatalog
📈 Small Reports Improvements: We’ve made a few quality of life improvements to the bird’s eye report, including having the header and first column frozen as you scroll around the table, and consistent filters for services, service groups, teams, owners, and levels regardless of the selected options.
IntegrationsAPI
🏃‍♂️ Continued performance improvements: You’ll notice large performance improvements across the board – our public API response times are improved by 5x on average, and we’ve shaved 20% off response times for in-app actions.🔽 GitLab projects filter: In the GitLab settings page, you can filter out specific groups and private repositories so that they don’t show up as you’re importing or scaffolding new services.
ScorecardsEng IntelligenceCatalogIntegrationsSettings & Permissions
🚧 Remove Users: In the permissions page, you can now remove users from Cortex.💻 Expand Number of Deploys in Executive Report: In the executive report, you can now expand the number of deploys to see what services have been deployed to each environment.👁️  Azure and Bitbucket in Service Discovery Audit: The discovery audit now shows services discovered in Azure and Bitbucket that aren’t mapped to existing services in the catalog. To add these to your service catalog, simply click the plus button and follow the onboarding steps. This is the last of the updates to the discovery audit. If you have any feedback, please let us know!❓ Help Desk Guides: We’ve updated our Scorecards guide in the help desk.
ScorecardsWorkflowsCatalogIntegrationsGitOps
✨ Pagerduty Auto-Discovery: Similar to our automatic “best-guess” mapping of projects for Sentry, Sonar, Datadog and other integrations, we will now automatically map your service in Cortex to a corresponding service in Pagerduty if the x-cortex-tag or service names match!👁️  Datadog and Newrelic in Service Discovery Audit: The discovery audit now shows services discovered in Datadog and Newrelic that aren’t mapped to existing services in the catalog. To add these to your service catalog, simply click the plus button and follow the onboarding steps.Scorecard rulesWe’ve added support to query your K8s resource spec JSONs using JQ e.g. jq(k8s.specs, "[].resources.etc > 0 | .length") > 1🏗️ Scaffolder Improvements: We’ve updated the @cortex_inputs variable we pass to your template with information about the user that ran the scaffolder.❓ Help Desk Guides: We’ve added a guide for Ladders and Levels in the help desk.
WorkflowsCatalogIntegrations
👁️  K8s in Service Discovery Audit: The discovery audit now shows k8s resources that aren’t mapped to services. To add these to your service catalog, simply click the plus button and follow the onboarding steps.🏗️ Scaffolder Improvements: We’ve made some small but impactful updates to the Scaffolder experience based on your feedback. Descriptions for the template inputs properly display links that will open in a new tab, and all multiple-choice options now are autocompletes instead of dropdowns.↕️  Keyboard support for the global Search Bar: You can now use the up and down arrow to navigate through the search bar. Pressing enter will take you to that object’s page.❓ Help Desk Guides: We’ve added a guide for Teams in the help desk.
ScorecardsInitiatives
🪜 Ladders in Scorecard Builder & Revamped Edit Scorecard Page: We’ve updated the Scorecard editor and brought the Ladders right into this page, to provide a unified editing process for both. A couple of improvements we’ve been able to make now that everything is on a single page:
  • If you’re using ladders and add a new scorecard rule, we’ll show you a warning so that you know that all rules are not in a ladder.
  • If you delete a rule that is in a ladder and the level is now empty, you’ll see a toast prompting you to fix that level.
  • To delete ladders from a Scorecard, simply delete all levels.
❓ Help Desk Guides: We’ve updated our Initiatives guide in the help desk.
ScorecardsWorkflowsCatalogIntegrations
👁️  Service Discovery Audit: It’s important to determine whether your catalog is fully comprehensive and covers all the repos, k8s deployments, and more across your engineering surface area. To solve this problem, we’ve built a Discovery Audit tool where you can see repos that haven’t been imported, with the option to ignore discovered services that aren’t necessarily relevant to the catalog.👷‍♂️ Scaffolder Improvements: When you register templates, you can choose to display the template’s README during the scaffolder flow. We’ve also added support for descriptions for the input fields, so you can explain what each field means.💯 Revamped Scorecard Builder Flow: We’ve updated the flow when you create a new scorecard to guide you through each step, making it easier to get a valuable Scorecard up and running.
ScorecardsCatalogIntegrationsAPICQLGitOps
🧬  Dependency Graph Filters: You can now filter dependencies depending on their source within the dependency graph, e.g., if you only want to see dependencies defined in cortex.yaml and hide edges that were synced from Datadog. Admins can also trigger a dependency sync with APM from the graph page.👯‍♀️  Teams API: You can now get, create, and update teams using the public API.❓ Help Desk Articles: We’ve added two new articles to the help desk – Importing Services and Basics of Using the Catalog – and updated the CQL docs to reflect the latest capabilities we’ve added. If there’s anything in particular you’d like us to cover, leave a comment and let us know.💯  Scorecard Rules:
  • Support for Snyk’s priority score and “age of issue” e.g. snyk.issues.filter((issue) => (issue.priorityScore != null or issue.priorityScore > 70) and issue.publicationTime > duration("P30D")).count < 10
Scorecards
💯  Scorecard Rules:
  • Check the number of SLOs that match a given name e.g. slos.filter((slo) => slo.name.matches("*-prod")).count > 2.
CatalogIntegrationsAPIGitOpsSettings & Permissions
👯‍♀️ Cortex Managed Teams: We’ve released support to manage team memberships directly within Cortex. When you go to create a team, you’ll have the option to sync members from an identity provider group (like Okta or GH Teams) or manage the members manually through Cortex.🌎  Dependency Overhaul + Datadog Sync: We’ve added a new dependencies API which lets you send dependency information to Cortex programmatically and merge that information with dependencies declared in the Service Descriptor YAML. We’re also enabling a periodic sync with the APM data in Datadog, allowing you to keep the dependency information up to date with the latest tracing data. We’ll automatically map dependencies from Datadog based on their service tag, or the serviceName field in the x-cortex-datadog section of the YAML.🚫 No Permissions Page: If users who are not admins try to visit any Settings pages, they’ll be redirected to the no permissions page.
ScorecardsEng IntelligenceCatalogInitiatives
❓ Executive Report Unowned Services: If you have any unowned services, you can click the info icon to see the full list.🔽  Initiatives Filtering Details: You’ll now be able to see initiative filtering information in the details section under prioritized rules.⚠️ Unsaved Changes Warning: If you’re editing a service, scorecard, initiative, or team and you try to leave the page while you have unsaved changes, you’ll see a popup notifying you to save before leaving. Hopefully this change will make life easier, especially if you’ve lost changes before by accidentally navigating away from the page by mistake.💯 Scorecard Rules:
  • Check if any or all of a service’s owner group names match a given regex e.g. owner_groups.anyMatch("team-.*") and owner_groups.allMatch("team-.*")
ScorecardsWorkflowsCatalogCQL
💄 UI Improvements: We’ve been focusing on improving the experience throughout the app this week and will continue to do so.
  • If you’re creating a new service in the Scaffolder, we’ll automatically fill in the name and tag for the service based on the repo details that you input.
  • After you delete an item, such as a service, you’ll see a toast that it was successfully deleted (or an error if something went wrong).
  • The edit service UI no longer allows service groups with whitespaces.
  • In the Query Builder, we’ve added a list of example queries to provide inspiration for what kinds of queries are possible with CQL:
Is there an update you’ve been waiting for that hasn’t happened? Let us know!💯 Scorecard Rules:
  • Custom data variable names in CQL can now contain colons, slashes, brackets, and other non-alphanumeric characters. Thus, you can write a scorecard rule like custom("this/is@now\"a-valid_name") = 1
  • Fixed a bug where JQ queries on git file contents e.g. jq(git.fileContents("my-file.yaml"), ".key1.key2") was marked as invalid.
ScorecardsWorkflowsEng IntelligenceAPICQL
🔕 Disabling Notifications through CQL: Admins can now limit notifications to specific services using CQL. You can test your query using the Query Builder and once it’s ready, just add it in the Settings page.👷‍♂️ Improved Scaffolder Errors: If the scaffolder fails as you’re running it, you’ll see better error messages that explain what went wrong along with a “Previous” button to be able to modify your inputs and re-run.📈 Executive Report: We’ve added a progress report for all Scorecards and the number of endpoints to the executive report.
ScorecardsWorkflowsEng IntelligenceCatalogIntegrations
👷‍♂️ Scaffolder (previously called Service Creation): We’ve added support for opening pull requests! This unlocks a few new use cases, such as creating services into a monorepo structure or adding templated one-off files/directories to existing services, like infra modules, CI scripts, etc.If you’re an admin, you can add templates in the Settings page and specify whether the templates creates a new service or adds features to an existing service.* This feature is not yet supported for Bitbucket💯 Scorecard Rules:
  • Check that SonarQube is set for a service
  • Support for YAML parsing in jq, for example jq(git.fileContents("circle.yml"), ".field")
👨‍💼 Executive Report: In the overview section, we’ve added the number of deploys in the last 7 days.
ScorecardsEng IntelligenceSettings & Permissions
📊  Reports: We’ve made a couple exciting updates to the reports page. There are now 5 report types - Bird’s Eye, Executive, All Scorecards, Progress, and Report Card.
  • The Executive Report provides a holistic view of your engineering organization across services, scorecards, and teams.
  • In the Bird’s Eye view, we’ve made Ladders a first class citizen. If the Scorecard you select has levels defined, you can toggle the columns between Rules and Levels. In aggregate views, you can quickly drill into the cell to see which services fall under that section.
  • If you want to see scores across all scorecards in a single view (with the columns being each of the scorecards), you can use the All Scorecards report. This used to be the report in the Birds Eye view when no scorecard was selected.
📕  Read Only Role: We’ve added a fourth role called “Viewer”, which is – as you’d expect – a read-only user. API Keys also now have a read-only option, which you can set when creating a new key.
ScorecardsInitiatives
🔎  Global Search: We’ve added teams, scorecards, initiatives in addition to services to our search bar so that you can easily find and navigate throughout the app.🔢  Query Builder CSV Export: You can export your query results to CSV by clicking the “Copy to CSV” button.
ScorecardsCatalogCQL
🕵️ Scorecard Filtering using CQL: Choose what services a Scorecard applies to through CQL expressions (rather than just service groups).To update your existing Scorecards, just click “Edit Scorecard” and in the filtering section, switch “Filter by” to “Query”. You’ll be able to input your CQL expression or use the CQL builder to help you.🔎  Global Service Search: You’ll notice we’ve added a snazzy search bar to the new menu. You can search for a service using the name, tag, or description.⤵️  Importing Services Flow: We’ve cleaned up the UI around importing services, making it much easier and simpler to get setup with Cortex.
ScorecardsIntegrationsCQL
🍫 New Menu bar: We heard your feedback (and felt it ourselves) - the old way to navigate around Cortex was difficult and unclear. We’ve released an overhaul of navigation and are excited to hear your thoughts!New Scorecard rules
  • Links: sometimes just counting links isn’t enough - now you can also check that the links in services have titles or URLs that match a regex pattern. These regex matches can even be chained together: link("runbooks").url_matching("www.*").title_matching("[a-zA-Z ]+").count
🔠  CQL Case Sensitivity: You can now use upper or lower case characters for AND, OR, TRUE, FALSE, NULL tokens. For example: git.fileExists("README.md") = FALSE and description != NULL)🏷️  Kubernetes Annotation Tagging: You can link your Kubernetes deployment to a Cortex service by adding an annotation to your deployment metadata. See the documentation for more information and an example.
ScorecardsCatalogAPI
📤 Bulk upload API for custom data: Custom Data is a powerful way of extending the catalog and building Scorecards tailored to your own use cases. Currently, you need to send one key/value pair, one service at a time. If you’re running an external process to pipe lots of data into Cortex, this can be a slow process. We just released a bulk upload endpoint, where you can send many keys for many services! Read more on our docs.
Integrations
📝 New & Improved Docs: Take a look at our new docs.👯 Teams URL: If you want to go directly to a team, just add ?tag=GROUP_NAME to the URL. If the team exists, you’ll be redirected to the team page, otherwise we’ll use the tag as a search param in the teams library. For example, the URL would be https://app.getcortexapp.com/admin/teams?tag=cortexapps/engineering
Last modified on November 18, 2026