Improvements 📈
- We’ve added support to configure Azure DevOps with a Service Principal using Entra ID. See our docs for more information.
- We’ve fixed an issue where the “Is override editable” setting on a User Input workflow block was not allowing users to edit the override value during execution for the “select” type. Users will now be able to manually change the selected value during workflow execution.
- We’ve fixed a bug where initiative reminder notifications that failed to send will attempt to resend all notifications, including those that were successful, resulting in additional noise during initiatives. Going forward, only notifications that failed to send will be retried. You can see notification logs in the Settings page.
- We’ve resolved an issue where pull requests could appear multiple times in Eng Intelligence metrics explorer and trace views. PRs are now deduplicated to ensure accurate analysis.
Improvements 📈
- We’ve added support to automatically pass in the entity context to entity-scoped workflows. Workflows that are linked from the description within Scorecards will now automatically pass in the entity ID, preselecting the entity to run a workflow against instead of the user having to select it themselves. You may also do this by manually appending the Cortex entity ID or entity tag to a workflow link. Learn more in our docs.
- We’ve added support for defining custom icons with the create or edit entity type API. See our API documentation for more details.
- We’ve resolved an issue where the same user could appear multiple times in Eng Intelligence filters. All entries with the same email identifier now map to a single name and appear as one unified entry in Eng Intelligence filters.
[Public beta] AI Impact Dashboard for GitHub Copilot: You can now measure adoption and impact of AI coding tools, starting with GitHub Copilot, across your engineering teams. This dashboard is in a public beta. Learn more in our docs.[Public beta] Custom views and dashboards in Engineering Intelligence: Easily create shared views of your key engineering metrics across your organization. Whether you’re tracking team delivery, reliability, or AI adoption, you can now design dashboards that bring your most important insights together. Learn more in our docs.New Integration UX: Our all new integration configuration experience is live for all cloud tenants as of today. The new interface will make it easier to discover, configure, and manage all your integrations in one organized place, with better categorization of integration types, improved testing capabilities, and clearer visibility into integration health and issues through our new integration logs. Learn more in our docs and please reach out with feedback!AI Docs Assistant in Cortex: We’re excited to introduce our AI Docs Assistant in the Cortex app experience. Access Docs Assistant via the Cortex search or Cmd+K, and ask questions in natural language, like how to configure an entity, or how to set up a Scorecard. This puts Cortex’s documentation and user guide knowledge base right at your fingertips in the Cortex app.Improvements 📈
- We’ve added a new Kubernetes Deployment Baseline Scorecard template to help teams enforce a minimum set of standards for services running on Kubernetes. It validates resource requests/limits, proves, container image hygiene, Git branch protection to ensure workloads are safe and reliable to operate in production.
Improvements 📈
- We’ve improved how tenant information is stored in the browser, so users will be prompted to enter their tenant name less frequently, making it easier and faster for users to log into Cortex.
- We’ve added the option to select from our generic icon list, in addition to our cloud icons, for custom entities to mirror the options we provide for icons in workflows and plugins.
- We’ve added Scorecard name to the delete scorecard confirmation modal, giving you more confidence and reducing risk when performing scorecard list management
- We’ve fixed a bug where ladder-based rules were not appearing as expected when filtering on failing rules on an Initiative.
- We’ve updated our Jira integration to support fine-grained API tokens with scoped permissions, replacing the legacy Browse Users and Groups permission that’s being phased out by Jira. If you’re setting up a new Jira connection, please refer to our updated docs for the correct scope configuration.
- We’ve improved our Dynatrace integration to reduce the number of calls needed to get SLOs for an entity, making the integration more performant overall.
Improvements 📈
- We’ve added a “Mine” tab to CQL reports. Now you can toggle between viewing all entities and just your entities directly on a CQL report the same way you can in other pages in Cortex, like the catalog pages.
- We’ve improved Executive Report performance, particularly optimizing deployment data aggregation and visualization.
- We resolved an issue where
git.codeSearch()in CQL ignored the path parameter for GitHub repos. Scorecards now return accurate results limited to specified file paths.
Remote Cortex MCP is now GA: The remote server makes it easier and faster to access the Cortex MCP to query information in natural language via your favorite LLM. Learn more in our docs and check out our MCP Prompt Library for examples.If you are already using the Cortex MCP, we’d love your feedback!Entity sidebar customization: The entity details page sidebar is a space to pin and surface important metadata related to your entities so that users can instantly understand what’s important. We’ve expanded the data that’s available to include: entity relationships, links, and custom data. Additionally, users with permissions to “Edit catalogs” can further customize the sidebar view with a drag-and-drop interface to reorder and hide items, and apply these changes to all entities of a certain type. Learn more in our docs.Bug fixes 🐛
- We’ve fixed an issue where CQL reports that have outdated data will show an incorrect last refreshed timestamp. Now CQL reports that need to be refreshed will show you that the data is expired, and encourage you to refresh to update the report.
Concept of “Mine” in Cortex MCP: You can now directly ask the Cortex MCP about what you own in Cortex. For example, ask “Show me services that I own,” or “show me how my services are performing against a certain Scorecard.” This allows you to directly filter for information most relevant to you. Learn more about the MCP in our docs.Engineering Intelligence Improvements in Cortex MCP: The Cortex MCP now makes it easier and faster to use Engineering Intelligence metrics by adding built-in awareness of supported aggregations and valid sorting options for each metric, ensuring accurate results and smoother metric exploration.If you’re using the local MCP, make sure to pull the latest.Improvements 📈
- We’ve released a search improvement that will boost services, domains, and teams over other entity types to address customer feedback about infrastructure resources from AWS, Google Cloud, and Azure cluttering search results.
- We’ve improved notification logs to make it easier to see what was delivered:
- You can now filter by delivery status to quickly view only successfully delivered notifications.
- When you hover over a recipient, you’ll see a tooltip with the list of Slack channels or email addresses that received the notification, and you can click through for more information.
- The list of recipients for notification logs is now sorted alphabetically.
- We added a “last updated” timestamp to the left of the refresh button on the entity overview page for AWS details, so users can see when the information was last refreshed.
- For all domain filters, you’ll now see both the name and tag (e.g. “Domain name (Domain tag)”) to make it easier to filter by the domain you’re looking for.
- We’ve fixed a bug where the “Restrict to initiator-only” toggle setting on Workflows was not retaining its state when the Workflow was duplicated.
- We resolved all undefined or missing failure reasons in notification logs.
- We fixed scrolling issues in the notification log details view.
Engineering Intelligence in Remote Cortex MCP (Beta): You can now query and access your Engineering Intelligence data directly through the Remote Cortex MCP server. This makes it easier than ever to surface key performance metrics without leaving your workflow. Learn more in our docs and reach out to your Cortex account management team for access.Improvements 📈
- Custom scheduled reminders for Initiatives now supports sending notifications to team channels. Note: This is enabled on by default. Please adjust your Notification settings if this is not your desired setting.
- We’ve updated initiative completion percentages to accurately reflect only entities and rules that are applicable and evaluated for the Initiative.
- We’ve fixed an issue where initiatives could incorrectly show 0 passing entities.
- Initiative notifications are now only sent to entity owners with active action items. If all entities pass requirements, no notification will be sent to the owners of the passing entities.
- All entities in the initiative scope are now displayed with only their applicable rules reflected in rule counts. Completely exempt entities will show “0/0 rules” to indicate they are not part of the evaluation.
- We’ve resolved an issue where failing rules were missing from an initiative’s entity filter.
New Cortex Academy Course: Understanding Engineering Intelligence: Learn how to measure, analyze, and improve engineering performance using Cortex Engineering Intelligence. This new course shows you how to explore metrics with Metrics Explorer, track delivery and reliability through out of the box dashboards, and extend analytics with custom metrics and user labels. You’ll learn how to turn insights into action using Scorecards, Initiatives, and custom dashboards and the course includes real-world examples, configuration walkthroughs, and best practices for driving continuous improvement across your engineering organization.Improvements 📈
- We’ve added the ability to sort any column in CQL reports.
- If you’re using GitHub vulnerabilities, we now support GitHub Copilot secret scanning alerts that look for passwords.
- We’ve fixed an issue where long descriptions in Workflow run confirmation was being cut off by the window size. Workflow run confirmation modals are now fixed size and scrollable, ensuring text and buttons are visible to users without resizing their browser window.
- We’ve fixed an issue where the user is incorrectly redirected to an invalid URL after registering a Scaffolder template. After successfully registering a Scaffolder template, users will now see the template on the Scaffolder list page.
Engineering Intelligence in Cortex: We are thrilled to announce that Engineering Intelligence is now a core Cortex platform capability and included for all Cortex customers at no additional cost. This update reflects our commitment to engineering excellence by empowering you to track, measure, and improve delivery and reliability across your organization. We will enable access for everyone on Monday, October 20th. Learn more in our docs and reach out to your Customer Success team to learn how to get started with Engineering Intelligence today.
At IDPCON, we announced a lot of exciting new features that are now available in beta:
- AI Impact Dashboard for GitHub Copilot: Measure adoption and impact of AI coding tools, starting with GitHub Copilot, across your engineering teams. Learn more in our docs.
- Custom views and dashboards in Engineering Intelligence: Easily create shared views of your key engineering metrics. Whether you’re tracking team delivery, reliability, or AI adoption, you can now design dashboards that bring your most important insights together. Learn more in our docs.
- Engineering Intelligence for Cortex MCP: You can now access Engineering Intelligence data directly in the Cortex MCP, enabling richer AI-assisted insights, not only into engineering performance, but across your entire Cortex ecosystem. Learn more in our docs.
- Remote Cortex MCP: Our new remote server makes it easier and faster to access the Cortex MCP to query workspace information in natural language via your favorite LLM. Learn more in our docs.
- New integration UX with improved testing capabilities and error logs: A complete overhaul of how you manage integrations in Cortex, with improved navigation, categorization, and troubleshooting capabilities. Learn more here.
AI readiness & AI governance Scorecards: Building and shipping AI responsibly starts with strong foundations. Cortex now helps you assess and track your organization’s AI maturity with two new out-of-the-box Scorecards:
- AI readiness Scorecard: Evaluate your teams’ infrastructure, data, and workflows to identify gaps before scaling AI adoption.
- AI governance Scorecard: Track compliance, security, and responsible AI practices to keep your org aligned as models evolve.
- You can now filter by ‘Entity types’ on the Scorecard details page, allowing easy filtering and searching for specific entity types on Scorecards that apply to many types of entities.
Cortex GitHub App Permissions UpdateCortex GitHub App Permissions Update: We’re updating the Cortex GitHub App to request
read:org and manage_billing:copilot permissions to support Copilot adoption and impact metrics in Engineering Intelligence.Action: Please re-authorize the Cortex GitHub app in your GitHub org to grant permissions and begin collecting Copilot adoption and impact metrics.Scorecard Rule Exemption Approvers: You can now configure to enable rule exemptions notifications to be sent to specific users when creating & editing Scorecards. When “Enable user-specific notifications” is enabled for a Scorecard, users can select a specific user to notify of the rule exemption when requesting it. If this is disabled, rule exemption notifications will continue to be delivered to all users with permission to manage rule exemptions. For larger teams, this will help with notification management, and ensuring the right person is notified of a request. Check out this docs page for more information.Improvements 📈
- Our docs site has a refreshed look. You can now find the Solutions and API content in separate tabs along the top of the page.
- We’ve added two new Scorecard templates
- SOC2 Compliance: This template helps teams ensure their services are aligned with SOC2 requirements by tracking audit-related controls and standards, making it easier to demonstrate compliance readiness.
- Ownership Verification: This template verifies that entities have clear, manually confirmed ownership, ensuring accountability and accurate entity ownership records.
- We’ve added descriptions to Reports pages to help users retain context as they navigate through individual reports pages
- We resolved an issue where filtering by failing rules in Initiatives sometimes returned incorrect results. Filtering now accurately reflects failing rules.
We have updated the default time range for the executive report from 30 days to 7 days. This improves first load performance and prevents the page from crashing in certain cases with large amounts of data, while we resolve the underlying issue with the Executive Report.
Ability to re-evaluate Scorecards by Entity via the API: You can now trigger a Scorecard re-evaluation for a specific entity directly through our API. This gives you the flexibility to reduce the frequency of scheduled evaluations and instead re-run them only when an entity changes. Learn more in our API docs.Configuring entities via the UI: We’ve updated the layout of our configure entity pages to support two new UI configuration options - Jira and SonarQube. We’ve also updated the logic for mapping Jira work items to entities to allow users to mix labels, components, and projects in Jira registrations for an entity.Improvements 📈
- We’ve added a new Scorecard template for AI Maturity. Learn more about using Cortex to drive AI Maturity in the docs.
- We’ve added a new Workflow template to automate user access to GitHub Copilot.
- There’s now a partner-built plugin for Spacelift, available in the Cortex Plugin Marketplace. After installing, view information from your Spacelift account, including total stacks, healthy stacks, total resources, total runs, and more.
From Insight to Impact: Join us this afternoon for our live webinar on operationalizing DORA metrics with Ganesh Datta & Nathen Harvey, DORA Lead & Developer Advocate. Register here.Can’t make it live? Register anyway and we’ll send you the recording.Cortex Solutions: Operationalizing DORA Metrics: The newest Solutions course is live in Cortex Academy. Learn the four key DORA metrics, explore common pitfalls, and see how Cortex surfaces actionable insights with Engineering Intelligence and Scorecards.Improvements 📈
- We’ve updated our existing DORA Scorecard to align with the latest DORA metrics and best practices. The new template adds clearer rule descriptions, refined levels (Minimum → Elite), and updated checks to better guide teams on their path to Elite performance balancing both lagging and leading indicators.
Improvements 📈
- We’ve updated the
groupfilter dropdown to automatically filter out groups that are only no longer being referenced by an active entity. When “show archived” is enabled, the dropdown displays the full results including groups from archived entities. - Metrics Explorer now shows which date field is used by the filter, and users can choose from multiple date fields for PR metrics. When navigating from the Velocity Dashboard, the selected date field is carried over for consistency.
- When exporting Workflow YAML, it will now include any validation logic that has been added to User Input blocks.
Improvements 📈
- Users “Mine” view now includes teams in the All Entities catalog for consistency across the application.
- You can now filter by ‘Entity types’ on the Scorecard details page, allowing easy filtering and searching for specific entity types on Scorecards that apply to many types of entities.
- Engineering Intelligence dashboards now indicate that certain metrics (cycle time, time to first commit, and PR size) are not yet supported for Azure DevOps and Bitbucket.
- We fixed a bug with catalog types to allow users to switch between entity filter catalogs and entity relationship catalogs.
Scorecard evaluation improvementsWe’ve implemented a fix to Scorecard processing that ensures manual Scorecard evaluations are processed separately from scheduled evaluations. Moving forward, manual evaluations will no longer wait behind scheduled evaluations, and should instead start immediately.
Updated Status Page: Our status page can be found at https://status.cortex.io. This is a great place to stay informed about service updates and incidents.Due to a migration, historical subscriptions will be deprecated after August 31st, 2025. To remain subscribed to updates after that date, please resubscribe here by clicking the button on the top right.Scorecard rules and CQL
- We’ve added the
findingStatusobject as a field of application-level findings to CQL expressions for our Veracode integration. This improvement enables more accurate vulnerability filtering and reporting. Learn more in the CQL explorer.
- We’ve updated the UI to now use “work items” when referring to Jira, aligning with Jira’s updated naming (previously shown as “issues”).
- We’ve added column visibility toggles to tabs on the All Entities page, as well as the CQL Reports and Query Builder details pages. These will allow you to hide columns from the table view. You can find the toggles in the “Display” panel next to filter and search.
- We fixed a latency issue where manual Scorecard evaluations for single entities was not completing as expected.
- We fixed an issue where git-related CQL functions (e.g.
git.fileExists()andgit.fileContents()) were incorrectly evaluating against the GitOps source repository branch instead of the service repository’s default branch. These functions now correctly default to each service repository’s main branch unless explicitly overridden, ensuring accurate results for GitOps-managed entities.
Jira Metrics in Metrics Explorer: You can now explore key project management metrics from Jira directly in the Metrics Explorer! These metrics provide visibility into your development workflow and work patterns. This release includes the following metrics:
- Story points completed
- Work item lead time
- Work items completed
- Work items created
- We’ve added new “Last week” and “Last month” date filter presets for Eng Intel, plus updated existing filter names for clarity (e.g. “Last 2 weeks” is now “Last 14 days”).
- In GitOps settings, you can now specify the repositories for Linter checks. Learn more in our docs.
- We’ve resolved an issue where some Scorecards were missing the “Include entity’s children” toggle in the Entity Overview page.
Relationships API in Cortex MCP: The MCP now has access to entity relationships. To update, simply run
docker pull ghcr.io/cortexapps/cortex-mcp:latest.Axon Framework: We’ve launched a new integration system that connects Cortex Cloud with your internal on-premise tools. This lets you integrate internal systems without exposing credentials or modifying firewall configurations. Check out our support docs or contact your customer success team to get started.Cortex Solutions: Incident Management & Response Academy Course: Learn how to streamline incident readiness, response, and recovery using Cortex. This new course covers best practices and shows how to use the Catalog, Scorecards, Engineering Intelligence, and Workflows to reduce MTTR and improve confidence during on-call scenarios. Includes example configurations, walkthrough videos, and actionable next steps.Improvements 📈- We’ve added new time aggregation options to Engineering Intelligence’s DORA and Velocity dashboards. You can now view metrics by daily, weekly, or monthly intervals, making it easier to track short and long term trends.
- For manual approval blocks in Workflows, you can now add context for approvers. They will see this in the workflow notification and when they go to Cortex to approve a workflow.
- We’ve added blocks to CRUD Google Projects in Workflows!
- We’ve improved some confusing behavior where the “Include entity’s children” toggle on an entity overview page for Scorecards excluded the parent entity’s Scorecards. The toggle now works so that when “Include entity’s children” is on, it shows both parent and child entity Scorecards.
- We’ve fixed a bug that prevented entities marked “unverified” from being re-verified during an active verification period. Users can now update verification status mid-cycle when ownership or other key data changes.
- We’ve addressed inconsistent behavior prompting the user to save changes when navigating away after making edits to Workflow steps. Users will be prompted with the “Discard changes” modal if they have unsaved changes on a Workflow step.
Improvements 📈
- We’ve updated the default behavior for Bird’s Eye and All Scorecards reports to hide empty rows by default.
- Users will now see all workflows they can run and their own workflow runs under the “Mine” tabs in the workflows list and workflow runs list. The all tab will still contain all workflows & workflow runs for the organization.
- When running a Workflow, users will now be able to open the newly created repository and corresponding Cortex entity, if applicable, directly from the Scaffolder step itself. This enables easier “health checks” for newly created repositories.
- We’ve added support for dynamic entity selection in Workflows, allowing you to limit the entity list based on the user’s context and only showing entities owned by that user and teams they’re a member of. Simply toggle “Limit options to runner user’s scope” for the user input after selecting Cortex entity as the data source. Learn more in our docs.
- You can now restrict workflows so that only the person who kicked off the workflow can provide any required input during the Workflow run. To enable this, simple toggle “Restrict to initiator only” to on.
- Team Scorecard visibility on homepage: Previously, Scorecard calculations for team entities were incorrectly hidden from the homepage after recent releases. This has now been resolved:
- Team Scorecards are now properly displayed on the homepage
- When viewing “Mine” on a Scorecard that applies to team entities, teams you’re a member of will appear in the filtered view.
- We’ve fixed a bug where users were unable to edit the Scorecard evaluation windows in settings.
Ownership Recommendations Improvements: We’ve made several enhancements to our ownership recommendation system to provide more accurate and comprehensive suggestions. Our updated model now considers additional team mapping scenarios and has expanded the criteria for which teams can be recommended as owners. If you’ve previously reviewed ownership recommendations, we encourage you to take another look as you may see new, more relevant suggestions for your services and repositories.Have feedback on ownership recommendations? We’d love to hear from you in our feedback doc.New Cortex Academy Course: Understanding Catalogs, Entities, and Relationships: Build a strong foundation in Cortex by learning how to define, organize, and connect entities across your software ecosystem. This course covers best practices for structuring catalogs, creating custom entity types, modeling real-world relationships, and visualizing ownership and dependencies to support visibility, automation, and engineering excellence.Scorecard rules and CQL
- We’ve added support for reachability & riskScore to the Snyk vulnerabilities object. Learn more in the CQL Explorer.
- You can now check if a repository has code scan enabled for GitHub using
git.hasCodeScan().
- We’ve updated the recently runs section at the top of the workflows page to only show your workflow runs, as opposed to seeing all workflow runs across the organization.
- We’ve added a handful of new workflow templates, including ones to update an entity description, trigger a Humanitec pipeline with a callback, and update a JSON file in GitHub. These are examples that you can use as a starting point as you build out workflows and modify as needed!
- You can now add labels for values in dropdown inputs, giving you more flexibility for what a user sees during the workflow run.
- In Workflows, descriptions for user inputs are now templateable so that you can include context from previous steps.
- We’ve updated the Scorecard score calculations on the homepage to include scores that apply to team entities.
- We’ve fixed an issue where AWS Lambda entities incorrectly remained visible in the import screen after removing Lambda cloud control configuration.
- We’ve fixed an issue where the GitHub Create or Update File block failed to resolve a reference to a state object in the repositoryName field, causing the block to error out.
- We’ve fixed a bug where state object was not correctly resolved in the JSON payload when triggering GitLab pipelines from a Cortex Workflow.
- We’ve fixed a bug where audit logs incorrectly recorded an identity mapping event for GitHub, even when the OAuth flow was unsuccessful.
Engineering Intelligence General Availability with Enhanced Dimensions and DORA DashboardWe’re excited to announce that our all-new Engineering Intelligence experience is now available to all customers with Engineering Intelligence enabled, along with two powerful new features:
- Enhanced Dimensions: We’ve added richer and more flexible ways to explore Engineering Intelligence data! You can now group and filter data by key attributes like owner, user labels, groups, domains, service, custom entity types and more! We’ve also added integration specific attributes like environment for deployments and PR label for version control data. Learn more in our docs.
- DORA Dashboard: Our newest out-of-the-box dashboard gives you instant visibility into the four DORA metrics. This will make it easy to measure and track key quality and velocity metrics from a single view. Learn more in our docs.
Variables in Workflows: We’ve added support for mutable variables in Workflows. You can now declare variables on a Workflow and then use the new ‘Set variable(s)’ block to set and update their values. Other blocks can reference variable values via the new
variables field in Workflow state. Learn more in our docs.Validation for Workflow inputs: We’ve added support to define custom JavaScript-based validations on user input fields in Workflows, enhancing the user experience during a workflow run. Learn more in our docs.Improvements 📈- We’ve updated our default domain catalog to show all children entities associated with a domain, not just entities with type domain. Learn more in our docs.
- For Workflows, you can now define the custom response templates for failed workflow runs, in addition to defining the successful response. Learn more in our docs.
- When running a workflow, the outputs will now be open by default.
- We’ve added support to set the placeholder value of an input during the Scaffolder block in a Workflow. To do so, you’ll have to add
placeholderin_cortex_field_configurationsto your cookiecutter template. Learn more in our docs.
- We fixed an issue where entity counts for an initiative was displaying differently between the UI and CSV export.
- Who’s on call for the backend-server?
- Im investigating an incident for backend-server. Give me all the details: owners, recent deploys, runbooks, links, and dependencies.
- Show me the services owned by the platform engineering team.
- Show me the currently active Scorecards and how brain-app is performing. Give me ideas on how I can improve them.
Scorecard rules and CQL
- We’ve added support for testing CQL queries from the CQL editor. This will allow users to quickly write and validate queries on a select number of entities, evaluate the results immediately, and iterate from the same interface. Learn more in our docs.
- We’ve added support for
git.releases()to CQL. You can now query release information from GitHub, GitLab, and Azure DevOps in Scorecards. Learn more in the CQL Explorer.
- We now support nested forms in the user input block in Workflows! This enables creating array-like input objects as part of a workflow. Learn more in the docs.
- We’ve updated the Scorecard side-sheet to hide the “failure message” for passing rules. We’ve also made the “not applicable” rules section collapsed by default.
- We’ve resolved an issue where the Catalog quick access section on the homepage did not reflect custom catalog names. The homepage now fully supports customized naming - for example, if you’ve renamed “Services” to “Applications,” that change will now appear correctly on the homepage experience.
Scorecard rules and CQL
- We’ve added reachability to the Semgrep vulnerabilities object in CQL.
- In our docs, you can now click Ask AI in the lower right corner of the docs to ask a question and get an instant answer in addition using the standard search tool.
- The JavaScript block in Workflows now supports the
yamlandhcl2-parserlibraries, allowing users to easily parse and manipulate YAML and HCL data within their custom scripts.
- We are now hiding the on-call section of the engineering homepage if you don’t have an on-call integration configured.
Apiiro Integration: We’ve added an integration with Apiiro to aid in your Security focused Engineering Excellence Initiatives. You can now visualize risks, create Scorecards for security standards, query risks using CQL, and create security related Initiatives, including for SOC2 and Compliance. Learn more in our docs.New Cortex Academy Course: Understanding Workflows: Learn how to design and configure workflows in Cortex, from setting up logic and inputs to managing run history and GitOps. This course walks through real-world use cases and explores the full block library to help you automate processes like service creation, onboarding, and incident response.Improvements 📈
- When clicking run on a workflow, you’ll now see the workflow title and description in the confirmation modal.
- Scaffolder now supports repository visibility configuration. Previously, all created repositories were defaulted to private, but users can now specify whether the generated repository should be public or private. This visibility setting can be defined in three locations: directly within the scaffolder template, in the scaffolder block of a workflow configuration, or when running the scaffolder. Learn more in our docs.
- We’ve made a few bug fixes to the flow for creating a custom entity, including fixing the provided example for the specified schema. Learn more about creating custom entity types in our docs.
Engineering Homepage: Our all new homepage experience is now live for all customers! It provides a centralized, personalized view that surfaces relevant insights and entry points into Cortex. Learn more about the new homepage in our docs.Improvements 📈
- We’ve added deep linking support to our API explorer.
- We’ve added an AWS account & region filter to CQL reports.
- When using the Scaffolder, you can now choose to open PRs when using Azure DevOps and Bitbucket. We’ve also added support for creating repositories without creating a corresponding Cortex service. This brings our git integrations to full parity for the Scaffolder. Learn more in our docs.
- We’ve updated the scores tab for Scorecards to show progress based on the type of Scorecard you’re viewing. For points-based Scorecards, progress will be shown based on points. For level-based Scorecards, progress will be shown based on the number of passing rules. Learn more in our docs.
- You can now limit your Bitbucket configuration to only look at certain projects in the Bitbucket Settings page.
Ownership Predictions is now live in Research Preview!We’re excited to announce that Ownership Predictions is now available to all customers in Research Preview starting today! This new model uses Git signals to intelligently predict and surface the most likely owners of services helping teams resolve stale ownership data, streamline incident routing, and improve audit and compliance readiness. You’ll see these predictions in our new Ownership report under “Tools” and in entity pages.Please note this is an early feature which may change. Not all integrations are supported yet. We currently provide recommendations for:
- The last 6 months of data for entities with GitHub, GitLab, or Azure DevOps repositories. Monorepos are not supported yet.
- Teams that have configured identity maps. Navigate to Settings and in the left sidebar, scroll down to Identity Mappings.
Deprecation Notice: Group SubscriptionsOn Friday, June 20th at 9am PST, we will be deprecating group subscriptions**.** Today, subscribing to a group causes all entities associated with that group to appear in a user’s “Mine” view across the Catalog. As part of launching the new Engineering Homepage, we’re introducing more flexible, accurate rollups for ownership and visibility. These rollups render group subscriptions unnecessary.After June 20, entities surfaced via group subscriptions will no longer appear as “Mine.” If you currently rely on this behavior, we recommend looking at the groups you are subscribed to in the group subscription Settings page and reviewing entity ownership and transitioning to the new Homepage rollups for visibility across your teams and entities.
Deploy & Incident Metrics in the Metrics Explorer: You can now explore deployment and incident metrics directly in the Metrics Explorer! These metrics provide better visibility into your engineering efficiency and reliability trends. This release includes the following metrics:
- Deployment frequency
- Change failure rate
- Incident frequency
- Time to resolution
- We’ve updated the behavior on a team entity page to show inherited entities by default.
- We’ve added new PagerDuty Workflow blocks to the library, bringing us to 213 blocks total! You can now CRUD escalation policies, schedules, services, and team.
- We’ve made various improvements to the workflow create & edit flows. You will now need to define the workflow name in order to start editing your workflow.
- We’ve added a copy button to the input & outputs JSON in Workflow blocks.
- We’ve fixed a bug with toggles in GitOps settings for entity UI editing & importing
New Cortex Solutions: Developer Onboarding course in Cortex Academy: Learn how Cortex streamlines developer onboarding by centralizing knowledge, tracking progress, and automating setup to help new hires contribute faster.Semgrep Integration: We’ve added an integration with Semgrep to aid in your Security focused Engineering Excellence Initiatives. You can now visualize vulnerabilities, create Scorecards for security standards, query vulnerabilities using CQL, and create security related Initiatives, including for SOC2 and Compliance. Learn more in our docs.
Engineering Homepage (Beta): We’ve added a handful of new functionality and polish to the new homepage experience including:
- Added recent workflow runs as a section in the homepage
- Added the number of entities on the catalog quick access
- We’ve added Workflow blocks to set targeting rules in LaunchDarkly feature flag and adding role policies in AWS, bringing us to 194 blocks in our workflows library!
- We’ve added the ability to resize tables within reports! We’re continuing to add this functionality across the application.
- We’ve added an AWS account & region filter to the Scorecard details page.
- We’ve updated the Weekly Report logic to use the same Git data source selection as the Developer Homepage. This change eliminates stale PRs in notifications and now includes Azure DevOps and Bitbucket data.
- We’ve fixed a bug with entity related dropdowns.
- Deactivated users will no longer show up in dropdowns for users.
- We’ve fixed an issue where CSV exports of CQL reports didn’t match the column order shown in the UI. Exports will now preserve the exact column layout you see in the table view.
JavaScript block in Workflows: We’re excited to introduce the JavaScript block to Workflows, enabling users to write custom scripts directly within their workflow logic. With the JavaScript block, you can more easily handle advanced data transformations, implement complex control flows, and make external API calls on the fly. This added flexibility streamlines tasks like parsing dynamic inputs, chaining asynchronous requests, or tailoring outputs for specific integrations without leaving the workflow. The JavaScript block supports the ES2020 specification and the
fetch API. Learn more in our docs.GitOps for Workflows: You can now manage your Workflows using GitOps, similar to entities & Scorecards. Learn more in our docs.Improvements 📈- We’ve added more blocks to the Workflows library bringing us to 189 total! Recent additions include new ADO blocks to CRUD branches.
- We’ve added
identityMappingsByAliasto the Workflows context (context.initiatedBy) so that you can access different identity mappings for users for different configurations. The existingidentityMappingsobject in context uses the default configuration. For example, you can now docontext.initiatedBy.identityMappingsByAlias.github.configuration-aliasto get a users corresponding identity for that integration configuration. - We’ve made an update to the identity mappings page for all users so that they can set up their GitHub account for each GitHub configuration, not just the default. This will help ensure identity mappings are properly set up across many configurations if a person is using different usernames in different organizations.
- We’ve added the ability to call your internal services from a workflow HTTP Request action using Axon Relay. This is in public beta, and the functionality works for any internal REST endpoint, not just the listed integrations. Reach out to our team if you’d like to try it out!
- We’ve added policy IDs for VictorOps rotations to support additional filter sets beyond team ID.
- We fixed a bug where Initiatives incorrectly displayed all applicable Scorecard rules under the “Goal” section, instead of only showing the explicitly defined initiative goal, which is now displayed correctly.
- We’ve resolved an issue where Initiative notification emails were incorrectly dependent on Scorecard notification settings by separating the logic, ensuring Initiative notifications now function independently as expected.
New Engineering Homepage: We’ve started rolling out our new Engineering Homepage experience —designed to serve developers, managers, and executives with personalized views that surface what matters most. If you or your organization want early access, sign up here.Secret scanning from GitHub advanced security: We’ve added support for pulling secret scanning alerts from GitHub advanced security. These will be displayed in code & security with severity set to high. You can also query for secret scanning alerts in CQL rules using
git.numOfVulnerabilities and git.vulnerabilities and filter by source GITHUB_SECRET_SCANNING. To have Cortex start pulling alerts, you’ll need to grant us permission to read “Secret scanning alerts” from your repositories. Learn more in our docs.Improvements 📈- We’ve added support for running a Jenkins pipeline to the Workflows block library.
- You can now filter Workflow runs by workflow, who initiated it, and date.
- We’ve updated navigation from the Scorecards page to the bird’s eye report & progress report to preserve your selected filter preferences for a more consistent user experience.
- We’ve fixed an issue where the language field in Azure DevOps was incorrectly displaying file types like
.xlsinstead of actual programming languages, ensuring accurate language detection going forward. - We’ve updated Slack notifications to only report score drops from successfully evaluated Scorecard rules, ignoring failures caused by API or client errors like rate limits, to prevent false negatives.
GitHub vulnerabilities severity change in CQLWe’ve re-mapped Cortex’s vulnerability severity from GitHub’s
Severity field to their Security Severity Level where available in order to better align with the GitHub UI. GitHub recommends using this field as it is better aligned with the industry standards Common Vulnerability Scoring System.You may see different severity levels for GitHub vulnerabilities on the entity page and CQL related rules, like git.numOfVulnerabilities and git.vulnerabilities , may return different results.AWS blocks in Workflows: The block library now has AWS blocks to create IAM groups & roles, S3 buckets, and ECS instances. We’ve also added blocks to list instances and run ECS instances. You can learn more about building Workflows in our docs or suggest a block here.New flow to create plugins: We’ve made creating new plugins simpler! When creating a plugin, you can decide whether you want to create a repository from our cookiecutter template, or just upload your code. Learn more in our docs.Improvements 📈
- When editing Workflows, you can now resize the panel on the right to give yourself more space. The set width will be maintained for future editing of workflows.
- If you’re using GitOps, you’ll now see the location of the YAML file and the most recent GitOps log in the entity YAML page.
- We’ve added support to filter the team members tab based on a user’s role in the teams page.
- We’ve rolled out a new design for all multiselect inputs that will make it easier to see what’s selected.
- We fixed a bug that caused the .csv export from the All Scorecards report to fail.
- We fixed an issue where not all teams were rendering in the team filter on the Executive Report
- We’ve updated the descriptions in the entity verification flow to support markdown.
All workspaces have now been automatically upgraded to the new experience. If you have any questions, please reach out to our team.Cortex Academy: We’re excited to announce the GA launch of Cortex Academy, a new learning destination built specifically for Cortex customers! Cortex Academy is your go-to resource for diving deeper into product areas, features, and use cases. Whether you’re looking to onboard quickly, level up your understanding of advanced capabilities, or explore best practices, Cortex Academy has you covered.How to access: Click your profile icon in the bottom left corner of the Cortex app, then select Cortex Academy from the menu.Cortex blocks in Workflows: We’ve added 30+ Cortex blocks to the blocks library. Within Workflows, you can now easily create, update, or delete the following Cortex resources:
- catalog entities
- custom data
- custom events
- custom metrics
- deployments
- You can now click on table headers to sort the table, in addition to using the dropdown in the top right.
- We’ve added recently run workflows to the entity page.
- You can now duplicate CQL reports.
- We’ve made a number of improvements related to Initiatives including:
- Hide expired Initiatives on the entity page by default
- The “view all” link from the entity page will only be presented when there are more than 3 active initiatives
- The total count of active Initiatives will be presented in the sidebar of the Entity page (if active initiatives exist)
- Fixed an issue to ensure the Initiative details page is displaying the correct rule count summary
- The plugin libraries,
plugin-core@3.0.0andreact-plugin-ui@1.0.0, have been fully released and updated to remove the beta tag.
- PATs will not work for deactivated users in Cortex.
- Sorting The Bird’s Eye Report report by “points” is now rending in the proper sorting order.
Redesign automatic upgradeWe’ve been receiving a lot of great feedback on the new experience. Your workspace will be automatically upgraded to the new experience tomorrow, April 29th, 2025.
Improvements 📈
- All plugins in the marketplace now support dark mode 😎
- We’ve moved the Discovery audit from Tools into a “Discovered entities” tab in the all Entities page. This change places the list of discovered entities in the same location as the import button, making it easier for you to find and import newly discovered entities.
- We’ve fixed an issue that didn’t show the correct rules needed to pass an Initiative on the Initiative details page
- We’ve fixed an issue with how errors and nulls were represented in the CSV export of a CQL report
- We’ve fixed an issue where archived teams were showing in Engineering Intelligence
New Workflows Run View: We’ve revamped the UI when a user is running a workflow. It’s now simplified to focus on the workflow steps and gives more space for inputs & outputs. To view the full workflow configuration, you can click the “View flowchart” button in the top right.Async HTTP block in Workflows: You can now add async HTTP actions in Workflows! This will pause execution until a callback API is invoked or the configured timeout occurs, enabling long lived steps that need to be executed outside of Cortex – for example, running a long CI deploy pipeline in your CI/CD tool as part of a broader Workflow. Learn more in our docs.Plugins in the new experience: As part of the redesign, we’ve been investing in upgrading our plugins toolkit to take advantage of the new features in the redesign. This includes ensuring plugins respect dark mode and your brand color.For existing plugins, we’ve updated the existing plugin-core package. Upgrade to version ≥3.0.0-beta.4 and follow the migration instructions within the README under the “Component library” section.For new plugins, you can use the new react-plugin-ui package. We’ve also created a beta cookiecutter template with examples using react-plugin-ui. The code can be found here. The template also has sneak previews of functionality such as support for routing and deeplinking.Note: This was released as a beta version.Improvements 📈
- We’ve moved owners, groups, & other key information about entities into the right side bar of the entity page. This ensures that key entity details are always visible as you navigate through the entity’s pages, as well as surfacing important live information higher above the fold in the overview.
- We’ve added active initiatives for entities in the overview page.
- We’ve fixed an issue where filters were not being persisted on export of a CQL report.
Google Cloud Observability Integration: We’ve added support for pulling SLOs from Google Cloud Observability into the catalog for entities & in CQL. Learn more in our docs.Improvements 📈
- Enhancements to existing GitHub branch actions
- GitLab project operations
- CRUD for Azure DevOps branch policies
- Additional ServiceNow blocks to fetch information needed when creating incidents
- We’ve added a 2 minute delay to workflow notifications to prevent sending them out if you’re actively inputting required fields on a workflow you recently kicked off.
- We added filters to the list Scorecards API. You can now filter based on entities, teams (that own entities), and groups.
- We added a new notification setting to allow users from external teams to receive notifications. The new setting is available in Notification Settings.
- Pull requests from archived repositories in GitLab will be excluded from work listed on the developer homepage.
- We’ve fixed an issue where CQL reports with no entity filters were returning null results instead of evaluating across all entities.
- We’ve fixed an issue where CQL reports were showing no results when the auto-refresh functionality was running.
All release notes going forward will be for the new Cortex experience.New GitHub blocks in the Workflows library: We’ve added 20 new GitHub blocks to our workflows actions library, including the ability to open a pull request, list teams & team members, & get commits. The following blocks require new permissions:
- “List deployments” and “Get deployment” requires the read “Deployments” repository permissions
- “Create deployment” requires the write “Deployments” repository permissions
- “Create team”, “Delete team”, and “Remove user from team” require the write “Members” organization permissions
- “Actions” repository permissions (write): Needed for the existing “Trigger workflow” block
- “Custom properties” repository permissions (write): Needed for the existing “Create or update custom property values” block
- “Search code” repository permissions (read): Needed for the existing “Find files” block
- You can now query an entity’s packages, using
packages(). Take a look at the CQL explorer for some examples. - We’ve added support for
git.vulnerabilities()from GitHub & GitLab. This enables you to write more complex queries than you were previously able to do with justgit.numOfVulnerabilities().
- We’ve added GitOps support for Bitbucket cloud when using basic auth, in addition to when Bitbucket is configured through the app or on-prem. To set it up, take a look at the Bitbucket Settings page.
- We’ve added support for importing projects from Google Cloud.
All release notes going forward will be for the new Cortex experience.Draft Initiatives: You can now create Initiatives and save them as drafts. This will allow you to create and iterate on Initiatives before having them go live and notify users. Learn more in our docs.Initiatives API: You can now manage initiatives via our API! We’ve added support for list, get, create, edit, and delete for Initiatives. Learn more in our API docs.Azure DevOps pipelines: You can now pull in pipeline run data from Azure DevOps for entities. This will be displayed in the CI/CD page. In Scorecards, you can add rules for
azureDevops.pipelines(), azureDevops.pipelineRuns(), and azureDevops.pipelineMetrics(). This allows you to monitor your CI/CD pipelines in Scorecards. To set this up for your entities, ensure your existing configuration gives Cortex permission for “build:read” and add the ADO project & pipeline information to your entity YAMLs. Learn more in our docs.Scorecard rules and CQL- We’ve added a lookback param to
rootly.incidents().
- You can now set up Workflows to send a Microsoft Teams message, similar to how you can send Slack messages in Workflows. Learn more about building workflows in our docs.
- The date input in Workflows now supports time.
- The API explorer now respects dark mode!
- When triggering an incident in Rootly in Cortex, you can now define the environment.
- In the Settings page, you will now only see installed integrations in the side nav. You can see the full list of integrations under browse all integrations.
- We’ve fixed a bug with seeing the description for owners in the entity page.
- We’ve fixed a few issues with setting up the GitHub configuration.
- We’ve fixed a few bugs with creating custom roles & assigning permissions to users.
GitLab vulnerabilities API changeWe’ve migrated GitLab vulnerabilities from using the Vulnerability Findings Rest API endpoint to the graphQL endpoint due to pending deprecation of the rest API.You might see more vulnerabilities on the entity pages and in CQL rules using
git.numOfVulnerabilities may start failing.All release notes going forward will be for the new Cortex experience.Workflows integration library: It’s now easier than ever to build Workflows! We’ve added integration-aware actions for common operations in addition to the actions currently available to build workflows. These leverage your existing integrations with third-party vendors so you’re able to perform operations in platforms like GitHub, PagerDuty, & ServiceNow with ease. Learn more about building Workflows & available blocks in our docs.Note: If you’re using the GitHub app, we require permissions to manage the organization members for the add & remove user actions.Automatically refresh CQL reports: You can now configure CQL reports to auto refresh! The minimum refresh window is 12 hours, and the maximum 2 weeks. Learn more about CQL reports here.Scorecard rules and CQL
- We’ve fixed a bug when using
remainingBudgetin CQL for Datadog SLOs.
- We’ve added support for number & date input types in Workflows.
- You can now select icons for Workflows & plugins! These will be displayed everywhere the workflow & plugin is referenced in Cortex, including side navs & tabs.
- Pull requests from archived repositories in GitHub will be excluded from work listed on the developer homepage.
- User mapping changes done manually will now be included in audit logs.
- We’ve fixed a bug that caused the Delete a User SCIM endpoint to incorrectly return a 403 error.
- We’ve fixed a bug where invalid Scorecard rules were silently dropped when added via the API. We will now show a 400 response with a detailed error message when our validation logic detects an invalid rule or filter.
Workflows integration libraryWorkflows help teams build golden paths & ensure great, consistent developer experiences & they’re even more powerful in the redesign!
- It’s now easier than ever to build Workflows! We’ve added integration-aware actions for common operations in addition to the actions currently available to build workflows. These leverage your existing integrations with third-party vendors so you’re able to perform operations in platforms like GitHub, PagerDuty, & ServiceNow with ease.
- By merging the Scaffolder into Workflows, you can add additional steps before or after the Scaffolder to standardize processes across your organization. Please note that in order to use the Scaffolder, you’ll need to create a workflow after registering the template.
- We’ve added a recently run workflows section to the list page, making it easier to run your favorite workflows frequently. You can also pin commonly used workflows to the top of the list view.
Better insight into progress for Scorecards & InitiativesScorecards & Initiatives are all about creating a culture of continuous improvement and our Scorecards in the redesign make it easier to see how your teams are progressing against the best practices you’ve set.
- When looking at a Scorecard’s details, you can now see the distribution of entities across the different levels to quickly understand how you’re tracking.
- In the Initiatives list & pages, you’ll be able to see progress against all Initiatives. This information is also available in the Initiatives tab in Scorecards.
- We’ve added “Create Initiative” buttons in the Scorecards & Bird’s eye report pages, making it easier to create a plan to improve directly when looking at results.
- In the Bird’s eye report, you can now filter based on “all of” or “one of” giving you more flexibility as you’re looking at the reports.
- In the All Scorecards report, you’ll be able to select the Scorecards that are displayed in the report, removing any that aren’t top of mind in the moment.
Improved structure for the entity pagesIn the redesign, you’ll see an improved structure for the entity pages. Cortex has a lot of information to surface & we’ve focused on bringing what’s important to the forefront
- We’ve grouped all the related integrations into single, contextual sections to make it easier to find what you’re looking for.
- If there is an active incident, you’ll now see that at the top of the entity page alongside the most recent deploy.
- All data from integrations links to its corresponding page in that integration so that you can more easily dive into the details if needed.
- GitHub & GitLab vulnerabilities now have their own dedicated pages, in addition to being displayed in the events timeline.
Redesign Public BetaWe’re super excited to announce the public beta for our new Cortex experience 🎉 ! We began this journey with the goal of creating a more cohesive experience by rethinking the entire experience from the ground up with three core pillars to guide our redesign:
- Actionability – We’ve designed each page to clearly communicate its purpose and the next steps you can take with structured layouts and prominent calls to action.
- Intuitiveness – We reimagined the information architecture to ensure that finding what you need is as seamless and straightforward as possible.
- Consistency – We invested in a robust design system to create unified patterns throughout the experience, so everything feels familiar and cohesive.
Rootly integration: We’ve added Rootly to our list of integrations! To set it up, simply add your API token in the Settings page and add your Rootly services to your YAML files in the
x-cortex-rootly section. After doing so, you’ll be able to see and trigger incidents in the entity pages and write Scorecard rules for them. Take a look at the docs for more information.Scorecard rules and CQL- If you’d like to filter Datadog monitors by environment in CQL, you can do so by filtering against the monitor tags. For example:
datadog.monitors().filter((monitor) => monitor.tags.anyMatch("env:prod")).length > 0. Take a look at other examples fordatadog.monitors()in the CQL explorer.
- We’ve added support for fetching a plugin’s blob in the API with the
includeBlobparam. Take a look at our docs for the get plugin API details. - We’ve added a patch endpoint for plugins, making it easier to update metadata or the blob without having to fully replace the plugin.
Owners update in API: When adding non-Cortex teams in
x-cortex-owners, we will now resolve the team to the corresponding automatically created Cortex team, instead of the specified team. This breaking change is to ensure consistency in how Cortex resolves ownership across the application.API keys API: In addition to creating API keys through the public API, you can now read, update, and delete API keys. To learn more about API keys, take a look at our docs.Secrets API: We’ve added support for managing secrets through the public API, in addition to being able to manage them through the Settings page. Secrets can be used in plugins & Workflows. To learn more about setting up secrets, take a look at our docs.Scorecard rules and CQL- We’ve added additional fields to the Azure DevOps work items object in CQL. Take a look at the CQL explorer to see the full schema & examples.
- We’ve added additional examples for SonarQube metrics to the CQL explorer
- We’ve updated our docs to better explain the expected behavior for mapping across multiple user aliases or multiple instances within your git providers or Jira.
- We’ve fixed an issue that prevented customers from uploading Scorecards that were previously deleted via GitOps.
- We’ve fixed a bug that prevented customers from creating an entity group Scorecard filter with uppercased group name via GitOps.
Scorecard rules and CQL
- We’ve added the ability to filter the PagerDuty analysis stats by priority. For example, you can now check the total incident count of P1 incidents in the last 7 days with
oncall.analysis(lookback = duration("P7D"), priority = ["P1"]).totalIncidentCount == 0. - We’ve added title & labels to the
git.pullRequests()object. - We’ve added storyPoints support for the wiql & object in
azureDevops.workItems(). Take a look at examples in our CQL explorer.
- We’ve added the run ID to the workflow context. It can be accessed using
{{context.workflowRunId}}or in jq with.context.workflowRunId. - GitHub repositories will now be regularly synced and kept up-to-date as new repositories are added via the Scaffolder tool or Scaffolder Workflow actions. In the Scaffolder, the “Sync repos” button now triggers a background sync so there is a slight delay before any new repositories are cached.
- We’ve updated the header of our email notifications.
oncall.usersWithoutContactMethods() CQL expression to be inclusive of all users in the rotation, not just those currently on-call. This update brings oncall.usersWithoutContactMethods() in line with the implementation of oncall.users() in order to provide a consistent experience.If you wish to remain consistent with today’s implementation of oncall.usersWithoutContactMethods(), you can update the CQL expression to oncall.usersWithoutContactMethods(onlyCurrentOncall = true).Additional flexibility in the Scaffolder: When adding a template, you’ll now be able to specify if you want to:
- Create cortex.yaml in git when creating a new service. By default, this is set to true for all templates.
- Create just a repository without creating a new service or opening a PR, simply set both to false. When running the Scaffolder in workflows, do not select “Create service”.
- We’ve fixed a bug with the list of plugins that appears in the Appearance settings pages. Previously, it was not including plugins in the “Service, Resource, or Domain” section if it also applied to a team.
Plugins Marketplace: We’ve been investing in our plugins marketplace & releasing a few quality of life improvements, including:
- When a new version of an installed plugin is available, the marketplace will show an “update available” badge and a button to install the update.
- When a plugin is already installed and current, Marketplace will show an “installed” badge, and the Install button for the plugin will be disabled.
- Marketplace will now refresh after installing or updating a plugin, to accurately show which plugins are installed.
- We’ve added entity verification Scorecard & CQL report templates to make it easier to track entity verifications.
- We’ve made several improvements to our Azure DevOps integration around data freshness, including a fix that will prevent outdated PRs from showing up on the homepage.
- We’ve fixed a bug in Workflows which prevented an entity-scoped workflow from appearing on some of the appropriate entity pages if exclusion groups were used for scoping.
User Labels for Eng Intelligence: We’ve added the ability to assign users to custom cohorts to be able to roll up metrics by labels in Engineering Intelligence. For example, you can create labels for engineering labels, stack or language, tenure, or location. For more information on how to get started, you can check out our docs.Improvements 📈
- We’ve added custom metric CQL rules to the rule builder when creating or editing Scorecard rules
- We’ve added the ability to adjust the pull request title and commit message in Workflows with a Scaffolder step.
- We’ve fixed a bug that could cause inconsistency between scorecard and service vulnerability information
Azure DevOps in Eng Intelligence: We’re now pulling Git metrics from Azure DevOps in Eng Intelligence! We’ve also added support for pull requests and reviews in CQL. You can read more about our Azure DevOps integration & the included Eng Intelligence metrics in our docs.If you would like to get started with Eng Intelligence, reach out to your customer success manager to set up a demo today!Improvements 📈
- We’ve added additional configurability for the fields you can set when a Jira ticket is created as part of initiatives. You can now add a custom description & label, as well as configure the entity name to include the “entity name” or “x-cortex-tag”. Learn more about creating Jira issues for Initiatives in our docs.
- You can now add a custom commit message and pull request title to the scaffolder step within Workflow runs.
- We’ve added the ability to ingest Maven package files and parse dependencies from your entities.
- We’ve added support for multi-alias identity mapping for git providers (GitHub, GitLab, Azure DevOps, & Bitbucket) and Jira. This enables you to map a single Cortex user to multiple aliases for a git provider if there are multiple configurations set up for an integration (eg multiple GitHub instances). This will allow users to see all pull requests across various projects on their developer homepage. Please note: Pre-existing mappings configured manually may display
unknownas the project alias. This will not affect how the app performs.
- We’ve fixed an issue where on-call notifications were not reflecting overrides on the PagerDuty schedules.
PATCH endpoint for entities: We’ve added a PATCH endpoint for entities. This is an upsert operation that will only set or replace the
x-cortex-XXX.YYY.property value.If the property is an array, by default, it’s full contents will be replaced, as opposed to just adding the additional value, but we have included a flag appendArrays to control this.If the entity does not exist it will create one with that YAML and return 201. By setting failIfEntityDoesNotExist=true , a 404 will be returned. See docs for details.Auto-discovery for New Relic: Similar to our automatic “best-guess” mapping of data for Datadog, Snyk, PagerDuty and other integrations, we are now automatically mapping an entity in Cortex to a corresponding service in New Relic based on the x-cortex-tag or entity names. Learn more in our docs.Actions are now Workflows: Actions are now deprecated. They have been removed from the side nav and entity pages.With Workflows, you can create far more powerful and flexible automated processes, replacing and expanding on what Actions previously offered.Improvements 📈- You can now create new API keys programmatically through the Cortex API.
- We’ve added custom metric CQL rules in the Scorecard rule builder to make it easier to add these rules to Scorecards.
- We’ve fixed a bug with searching for Azure DevOps work items in CQL.
- We’ve fixed an issue related to plugin scope which could prevent a plugin from appearing on the intended entity pages.
- We’ve fixed an issue with users being duplicated in the edit entity members page.
- If you’re syncing team member roles from integrations, we’ve fixed an issue resulting in duplicate roles.