Feature Requests

We would like to request a capability that allows the platform to capture and record team members who actively engage in an incident, even if they were not formally paged by the system. Proposed Functionality: Automated AI Capture: Enable the AI agent to automatically detect and log users who join the conversation or contribute to the incident resolution (e.g., via connected chat channels or platform activity) without an explicit page. Manual Entry Option: Provide an option for incident commanders or responders to manually add unpaged participants to the incident record, next the page on-call button for example. This feature would greatly improve the accuracy of our post-incident reviews (post-mortems) and provide a clearer picture of our true engineering resource allocation during critical events.

Description: Current filtering on the alerts page is limited to "Priority," "Status," and "Alert Title," which restricts efficient alerts triage. Please expand filtering criteria to include: Targeted Recipients, Source (e.g., specific runbook or alert rule), Summary, and custom metadata fields passed via integrations.

Hi Currently, AI SRE resources (including integrations, schedules, and configurations) appear to be restricted to the Project level. For organizations where AI SRE practices are standardized across multiple teams, managing these resources individually within each project is inefficient and creates significant administrative overhead. we propose that AI SRE resources be manageable at the Account or Organization level, similar to the architecture of the Harness Artifact Registry. This would allow centralized management while enabling seamless distribution across various projects. Key Requirements: Hierarchical Scoping: Enable the creation and management of AI SRE resources at the Account and Organization levels. Terraform Support: Introduce Terraform provider support for AI SRE resources. Manual replication across projects is currently a blocker for automated, enterprise-scale deployments. Cross-Project Accessibility: Ensure that centralized resources can be referenced or inherited by individual projects without requiring users to share a single project space.

Users need to manually add key events during incidents, but the relevant information is already in timeline entries or Slack messages. Specific Ask: Add right-click or context menu action on timeline entries and Slack messages to mark them as key events. One click should capture the content and timestamp directly into the key events list. Impact: Streamlines incident documentation during active response. Instead of copy/pasting from timeline to key events, users can mark them in context with a single action.

Hi Team, We would like a feature in AI SRE that provides an AI summary and other important metrics, such as MTTR after an incident, and also offers suggestions to reduce MTTR.

Hi Team, We want to Implement Harness AI to identify the root_cause of the failure stage/step by sharing the failed step logs with Harness AI Harness pipeline: Platform Full Prep and Release identifier: Platform_Full_Prep_and_Release projectIdentifier: boomi_releases Kindly please schedule a call and connect with us to understand the requirements by today asap. Thanks, Vishal Vaidya vishal.vaidya@boomiteam.com

We are looking to see if we could show MTTR details, such as where they spend most of their time resolving the issue and what could be improved in the process, in an AI summary.

We'd like to see Zoom meeting attendance data captured and displayed directly on incident records. Requested Feature: When a Zoom meeting is associated with an incident, automatically capture and display: Roster of all meeting attendees Join time for each attendee Leave time for each attendee Total duration each person was on the call Use Case: During incident response, we need to track who participated in war room/bridge calls and for how long. This information is valuable for: Post-incident reviews and timeline reconstruction Compliance and audit requirements Understanding participation and engagement during critical incidents Identifying the actual incident commander and key responders Technical Note: The Zoom API supports this via the GET /report/meetings/{meetingId}/participants endpoint, which provides all the necessary participant data, including join/leave times and duration. Current Workaround: Manually downloading Zoom reports and adding this information to incident documentation, which is time-consuming and error-prone.

We would like to have a feature in AI SRE, where we can ingest past incidents, so that the AI SRE becomes more context-aware and provides suggestions based on previous incidents.