Blameless announced a significant expansion to their integration with ServiceNow.
With this expansion of the connection between both platforms, users can now leverage Blameless to operationalize their use of retrospectives without compromising their standards for data governance and compliance defined within ServiceNow. This comes in addition to the already widely adopted connection between the Blameless incident response workflow and ServiceNow’s incident ticketing system.
Last summer, Blameless announced an integration to ServiceNow’s incident management ticketing solution to help DevOps and SRE teams streamline incident ticketing workflows and reduce future repeat incidents.
By extending the integration to encompass ServiceNow problem management, Blameless has made it simpler for engineering teams to carry their incident response workflow all the way from acknowledgement through retrospective and corrective action within Blameless. The outputs of that process are then automatically delivered into ServiceNow to eliminate any necessary double entry. This allows organizations who utilize both systems to capture all the benefits of leveraging Blameless’ retrospective tools to save them time and energy without compromising their data governance and compliance requirements defined in ServiceNow.
Additionally, users of ServiceNow who turn to Blameless for a superior retrospective experience will additionally be able to lean into the Blameless Slackbot for incident management, which automates most of the heavy lifting of retrospective creation and informs the rest. Retrospectives then push data into ServiceNow problem management to close the loop for engineering teams from response to root cause analysis and response or mitigation.
Benefits and Capabilities of the Integration Extension:
- Auto-create a Problem ticket: Blameless automatically creates a problem ticket when an incident is started from ServiceNow, Slack, Microsoft Teams, or the web user interface, and then links the ServiceNow incident to the Problem ticket.
- Link to the Problem ticket from the Retrospective: Blameless Retrospective users are able to navigate to the problem ticket with a link from the Retrospective page in the Blameless web user interface.
- Enable/Disable auto-creation of Problem tickets: Administrators have the option to enable/disable the auto-creation of a Problem ticket at the ServiceNow integration settings level.
- Configurable Retrospective custom fields: Users are asked to capture specific and higher quality data during retrospectives. Under the Retrospective settings, a list of custom fields of various types (short-text, paragraph, single/multiple choices) can be configured to enforce such best practices for all or specific retrospectives depending on the severity and type of the incidents. Additionally and optionally, when mapped to ServiceNow Problem custom fields, such retrospective data can be automatically updated into ServiceNow Problems custom fields.
- Reporting Retrospective custom fields via Reliability Insights: With this wealth of historical information gathered automatically and manually into Retrospectives, Blameless provides a powerful framework to Engineering organizations to further learn and improve upon incidents by extracting key insights using Reliability Insights, Blameless’s embedded data analytics and reporting tool.
"Synchronizing our Retrospectives with their Problem Management in addition to Incident Management allows our customers to bring their full incident response workflow into Blameless without compromising their use of ServiceNow for data governance and compliance. It really allows our customers to benefit from the best of both worlds,” said Jim Gochee, CEO of Blameless. "Our goal is to support engineering teams by providing them with a seamless workflow when dealing with the incident management process from beginning to end.”
The Latest
A major architectural shift is underway across enterprise networks, according to a new global study from Cisco. As AI assistants, agents, and data-driven workloads reshape how work gets done, they're creating faster, more dynamic, more latency-sensitive, and more complex network traffic. Combined with the ubiquity of connected devices, 24/7 uptime demands, and intensifying security threats, these shifts are driving infrastructure to adapt and evolve ...
The development of banking apps was supposed to provide users with convenience, control and piece of mind. However, for thousands of Halifax customers recently, a major mobile outage caused the exact opposite, leaving customers unable to check balances, or pay bills, sparking widespread frustration. This wasn't an isolated incident ... So why are these failures still happening? ...
Cyber threats are growing more sophisticated every day, and at their forefront are zero-day vulnerabilities. These elusive security gaps are exploited before a fix becomes available, making them among the most dangerous threats in today's digital landscape ... This guide will explore what these vulnerabilities are, how they work, why they pose such a significant threat, and how modern organizations can stay protected ...
The prevention of data center outages continues to be a strategic priority for data center owners and operators. Infrastructure equipment has improved, but the complexity of modern architectures and evolving external threats presents new risks that operators must actively manage, according to the Data Center Outage Analysis 2025 from Uptime Institute ...
As observability engineers, we navigate a sea of telemetry daily. We instrument our applications, configure collectors, and build dashboards, all in pursuit of understanding our complex distributed systems. Yet, amidst this flood of data, a critical question often remains unspoken, or at best, answered by gut feeling: "Is our telemetry actually good?" ... We're inviting you to participate in shaping a foundational element for better observability: the Instrumentation Score ...
We're inching ever closer toward a long-held goal: technology infrastructure that is so automated that it can protect itself. But as IT leaders aggressively employ automation across our enterprises, we need to continuously reassess what AI is ready to manage autonomously and what can not yet be trusted to algorithms ...
Much like a traditional factory turns raw materials into finished products, the AI factory turns vast datasets into actionable business outcomes through advanced models, inferences, and automation. From the earliest data inputs to the final token output, this process must be reliable, repeatable, and scalable. That requires industrializing the way AI is developed, deployed, and managed ...
Almost half (48%) of employees admit they resent their jobs but stay anyway, according to research from Ivanti ... This has obvious consequences across the business, but we're overlooking the massive impact of resenteeism and presenteeism on IT. For IT professionals tasked with managing the backbone of modern business operations, these numbers spell big trouble ...
For many B2B and B2C enterprise brands, technology isn't a core strength. Relying on overly complex architectures (like those that follow a pure MACH doctrine) has been flagged by industry leaders as a source of operational slowdown, creating bottlenecks that limit agility in volatile market conditions ...
FinOps champions crucial cross-departmental collaboration, uniting business, finance, technology and engineering leaders to demystify cloud expenses. Yet, too often, critical cost issues are softened into mere "recommendations" or "insights" — easy to ignore. But what if we adopted security's battle-tested strategy and reframed these as the urgent risks they truly are, demanding immediate action? ...