devopsy.kinsta.cloud

Tag: victorops

  • Splunk Pushes Into the Realm of DevOps

    Splunk Pushes Into the Realm of DevOps

    On the heels of its recent acquisition of VictorOps, provider of incident management software, for $120 million, Splunk is gearing up to expand its foothold in DevOps significantly.

    Rick Fitz, senior vice president of IT Markets for Splunk, said the provider of widely used operational analytics software in the enterprise sees a significant opportunity to expand its presence across a range of DevOps processes.

    Incident management is a natural extension of operational analytics, said Fitz, noting Splunk chose to acquire VictorOps because the investments the company has made in applying machine learning algorithms to monitoring IT events. That approach significantly reduces the number of irrelevant alerts being generated and provides actionable intelligence into potential events that could adversely impact IT operations.

    Most IT operations teams suffer from alert fatigue, Fitz noted, and most alerts are ignored because of a lack of context. The combination of Splunk and VictorOps will result in alerts that more precisely identify the root cause of any IT issue, he said, and a better overall “systems of engagement” for IT operations teams in keeping with DevOps principles.

    Splunk has been steadily expanding its focus on DevOps. Earlier this year the company announced Splunk Insights for Infrastructure, which IT organizations can host on an Amazon Web Services (AWS) public cloud to monitor IT infrastructure deployed anywhere. The latest versions of Splunk Cloud and Splunk Enterprise also make use of machine learning algorithms on top of a revamped metrics engine that enables IT administrators to monitor everything from CPU speeds and available hard disk space to temperature readings in internet of things (IoT) devices and sensors. Splunk recently also added connectors for Docker and Kubernetes, as well as the Apache Kafka messaging platform for streaming data in real time.

    IT operations and cybersecurity teams already rely on Splunk operational analytics software extensively to identify anomalies. By investing in machine learning algorithms and acquiring incident management software, Splunk is moving to turn all the data it analyzes into actionable intelligence, which then could be shared in real time with developers to ensure application availability and optimize application performance.

    While adoption of DevOps processes in traditional enterprise IT organizations remains spotty, IT vendors that focus on IT operations such as Splunk have clearly seen the writing on the wall. Fitz noted that investments made in machine learning algorithms, for example, will enable IT operations teams to more respond to changing application requirements with greater agility at a time when the IT environment has become exceedingly complex. That agility is critical for any organization engaged in digital business transformation, Fitz said, because invariably those efforts lead to more applications being deployed.

    It’s not clear the degree to which incumbent providers of IT operations software will be able to remain relevant in the age of DevOps. But most of them certainly have the financial resources to at the very least acquire a portfolio of DevOps tools that will enable them to exert a lot more influence than many of them have to date.

    — Mike Vizard

  • Splunk Acquires VictorOps: The End of the Road for Standalone IT Alert Management Tools?

    Splunk Acquires VictorOps: The End of the Road for Standalone IT Alert Management Tools?

    This week, Splunk, the leader in machine data intelligence, announced the acquisition of IT alerting solution VictorOps for $120 million. My congratulations to the VictorOps team for building a solid product for alert management and collaboration, demonstrating a wicked sense of humor and creating some cool T-shirts.

    While the acquisition makes sense on many levels, it does raise broader questions about the need for standalone IT alerting tools. Let me explain why IT alert management as a category faces strong headwinds and how these tools will need to evolve if they are going to remain relevant in a world driven by digital transformation.

    What Do IT Alert Management Tools Actually Do?

    When an IT outage or service disruption occurs in an enterprise, the first order of business is to restore operations back to normal. IT outages can cost you a lot (an hour of downtime can cost you upwards of $100,000 per hour), disrupt your customer experiences and derail employee productivity. To quickly troubleshoot an IT incident, you’ll need to notify the right subject matter experts who can collaborate together to pinpoint root cause for an outage.

    Every day, enterprise network operations center (NOC) teams receive hundreds of alerts from different IT management tools for monitoring, service desk, event correlation and configuration management. A certain percentage of these alerts demand urgent attention from NOC teams who are on-call and readily available for incident support.

    Enter IT alert management tools, whose job it is to manage the notification of messages to personnel based on predefined rules regarding who to notify for a given categorization of event or incident. Tools from PagerDuty, VictorOps, xMatters, OpsGenie and Everbridge alert the right team members using on-call schedules and notify them using a variety of channels including email, text, voicemail and chat. IT alerting tools help you manage the entire incident life cycle, using on-call schedules, alert routing rules and collaborative war rooms.

    Embedded Alert Context: The Missing Piece of the Alert Puzzle

    The fundamental challenge with scaling enterprise alert management is about establishing the right context for a flood of alerts that you’ve just received. Instead of forwarding every single alert that you receive, can you share actionable alerts that your NOC teams can immediately act upon?

    Your IT alerting tool needs the ability to correlate a bunch of alerts into a single event for faster acknowledgment and troubleshooting. Alert consolidation and correlation call for intelligence that can extract signal from the noise and compress alert volumes with the right inferences. Artificial intelligence for IT operations (AIOps) helps you do just that, by applying big data and machine learning techniques to event management data. With AIOps tools, you can handle events and minimize alert noise by delivering timely and actionable insights for incident support. This agility and insight, coupled with intelligent correlation to stay on top of major outages, helps NOC teams by focusing their attention on the incidents that truly matter.

    AIOps + Alert Management = Smarter Incident Management

    Without the ability to apply machine learning algorithms to alert floods, alert management tools act as “dumb forwarders” of IT alerts, inducing alert fatigue and adding to the overall noise. It’s time for alert management to get smarter and contextual with machine learning insights.

    Splunk’s acquisition of VictorOps is a clear sign that alert management tools as a standalone category can’t truly scale without a solid AIOps foundation. With artificial intelligence, IT teams can stop wasting valuable time figuring out incident triage and root cause analysis and ensure faster recovery from crippling outages with the right event analytics.

    — Deepak Jannu

  • Splunk Agrees to Acquire VictorOps

    Addition of Incident Management Leader to Create Collaborative, Analytics-Driven Platform for DevOps

    SAN FRANCISCO–(BUSINESS WIRE)–Splunk Inc. (NASDAQ: SPLK), first in delivering “aha” moments from machine data, today announced a definitive agreement to acquire VictorOps, Inc., a leader in DevOps incident management. Under the terms of the agreement, Splunk will acquire VictorOps for a total purchase price of approximately $120 million, subject to adjustment, to be paid in cash and Splunk securities. The acquisition is expected to close during Splunk’s fiscal second quarter, subject to customary closing conditions.

    “The combination of machine data analytics and artificial intelligence from Splunk with incident management from VictorOps creates a ‘Platform of Engagement’ that will help modern development teams innovate faster and deliver better customer experiences,” said Doug Merritt, President and CEO, Splunk. “This gives on-call technical staff an analytics-driven platform to monitor issues, resolve incidents and continuously improve. We are thrilled to welcome the VictorOps team to the Splunk family as we extend Splunk’s vision of using data as the backbone of IT.”

    “We founded VictorOps to give teams a naturally collaborative way to quickly resolve incidents,” said Todd Vernon, CEO, VictorOps. “By combining VictorOps incident management capabilities and the Splunk platform, organizations will be able to quickly resolve and even help prevent issues that degrade customer engagement. We look forward to joining Splunk and working together to help solve these complex challenges facing every Development and DevOps team.”

    AI for Collaborative Incident Management

    Customers around the world are demanding innovative digital experiences that place a burden on development teams to innovate faster than ever before; however, challenges such as vague alerts, reactive operations and siloed teams often get in the way of delivering high-quality customer engagements and fully embracing an IT strategy fueled by AIOps.

    To combat this, organizations are increasingly turning towards artificial intelligence (AI) and machine learning (ML) solutions to help them focus on critical aspects of the customer experience. By applying ML and AI to monitoring, event management and incident management data, Splunk and VictorOps will enable DevOps teams to speed resolution and learn from past actions to make proactive recommendations.

    Thousands of customers use Splunk® Enterprise to proactively monitor, visualize and get answers from their machine data. The combination of Splunk Enterprise and VictorOps will deliver a ‘Platform of Engagement’– combining monitoring, event management, on-call management and ChatOps. Ultimately, this enables modern engineering and operations teams to quickly solve problems in high-velocity deployment environments to maximize customer success.

    Nearly all of the purchase price consideration will be paid in cash, funded from Splunk’s balance sheet.

    Safe Harbor Statement

    This press release contains forward-looking statements that involve risks and uncertainties, including statements regarding the expected benefits of the acquisition of VictorOps, the impact of the acquisition on Splunk’s existing and future products and services, and the capabilities of VictorOps’ products and services, including when combined with Splunk’s. There are a significant number of factors that could cause actual results to differ materially from statements made in this press release, including: difficulties encountered in closing and integrating the merged business, technologies, personnel and operations; costs related to the acquisition; market acceptance of the acquisition and resulting products and services; Splunk’s inability to realize value from its significant investments in its business, including product and service innovations; and general market, political, economic and business conditions.

    Additional information on potential factors that could affect Splunk’s financial results is included in the company’s Quarterly Report on Form 10-Q for the quarter ended April 30, 2018, which is on file with the U.S. Securities and Exchange Commission. Splunk does not assume any obligation to update the forward-looking statements provided to reflect events that occur or circumstances that exist after the date on which they were made.

    About Splunk Inc.

    Splunk Inc. (NASDAQ: SPLK) turns machine data into answers. Organizations use market-leading Splunk solutions with machine learning to solve their toughest IT, Internet of Things and security challenges. Join millions of passionate users and discover your “aha” moment with Splunk today: http://www.splunk.com.

    Social Media: Twitter | LinkedIn | YouTube | Facebook

    Splunk, Splunk>, Listen to Your Data, The Engine for Machine Data, Splunk Cloud, Splunk Light and SPL are trademarks and registered trademarks of Splunk Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners. © 2018 Splunk Inc. All rights reserved.

    Contacts

    Media Contact
    Splunk Inc.
    Bill Bode, 415-706-1236
    bbode@splunk.com
    or
    Investor Contact
    Splunk Inc.
    Ken Tinsley, 415-848-8476
    ktinsley@splunk.com

  • 6 Must-Haves When Using Chat for Incident Management

    6 Must-Haves When Using Chat for Incident Management

    Over the last few years, teams have realized the benefits of sharing and distributing knowledge in chat applications such as Slack. Today, teams are extending the use of these applications beyond collaboration by embracing ChatOps. ChatOps empowers teams by bringing complex day-to-day operational work into shared chat channels. If done correctly, it drastically reduces context switching and increases the speed at which teams can tackle tough challenges.

    Companies are realizing incredible benefits by incorporating ChatOps into their incident management workflows. Chat channels provide hyper-effective means to alert teams of issues, take immediate action and collaborate with clarity and urgency. It is for this reason that companies including OpsGenie, PagerDuty and VictorOps have invested in integrating their incident management applications into chat applications such as Slack, HipChat and Microsoft Teams.

    ChatOps to the Rescue

    Ideally, users of a modern incident management solution need to have access to a multitude of features so that they can address specific challenges directly within the chat tool. During an incident, switching between applications to access and collaborate on the actionable data is a waste of time. Keeping the conversation and action in one place, where team members already are, is the key to a fast and successful incident resolution process. That is why ChatOps has emerged as an alternative to the war room concept.

    To get the most out of the technology and resolve problems more quickly and easily, here are six tips to consider when using ChatOps for incident management:

    1. Post Messages with Clarity

    The basic requirement for integrating any application within chat tools is to simply have messages posted within chat channels. However, there are three additional needs to consider when integrating an incident management tool into chat when increasing efficiency is the goal.

    • The integration must be able to post chat messages regardless where the incident originates and additional information added (monitoring, ticketing, or collaboration tools).
    • Messages need to be customized based on the specifics or severity of the incident. Often the basic message needs to be appended with tags or additional information fields.
    • If possible, include a button in the message that allow responders to take instant, prescriptive actions.

    2.  Control How Information is Shared

    Posting every alert and comment into a shared channel can quickly become overwhelming and is considered bad practice. A strong integration enables the creation of separate channels for specific responders and have direct control over what types of alert and follow-up messages are shown.

    A seamless integration also provides the flexibility to receive only the incident actions that are decidedly relevant. Low-priority issues that don’t require immediate action can be filtered and not sent to the chat stream, ensuring the team stays focused on what really matters.

    3. Accelerate Actions

    ChatOps transforms chat into a vehicle through which users take actions and deploy solutions. This virtually eliminates the need for operations teams to switch between applications when responding to an incident.

    Most integrations enable users to execute incident actions using text commands. This method is valid and often preferred. However, deeper integrations simplify tasks by providing interactive buttons that enable users to begin working on incidents with just a click.

    The value of responding to an alert by clicking a button extends beyond simple alert acknowledgement. Enabling all common responses (i.e. assigning an alert, taking ownership, adding notes, muting incidents, etc.) to be executed in this manner accelerates resolution and unlocks the real power of ChatOps.

    4. Instantly Retrieve Supporting Information

    A challenge of a long chat thread is that critical information can get lost within the communications or additional information may be needed. A user might have to leave the channel to look up important details and related information, such as looking at other open incidents, for example.

    The integration of an incident management system into the chat environment needs to allow users to access supporting information at any time. The ability to query not only additional details about a specific incident but also general information regarding on-call schedules and alert policies is a requirement. By empowering team members to access this data directly within the chat interface, they stay focused and are able to respond in the most efficient manner possible.

    5. Create New Alerts

    A common task when managing an incident is to create manual alerts. Again, requiring people to switch applications to complete this task is a distraction and slows the progress.

    Creating new alerts for a team or service right within the chat channel is a necessity. The incident management system then notifies the person on-call automatically. Having the ability to create an alert directly within chat empowers individuals that may not have direct access to the incident management system to report problems efficiently.

    6. Control Access

    When an incident occurs, it is important that corrective action is taken by only the people who are authorized to respond. Mapping (or linking) the chat users to the users within the incident management system enables this level of control.

    Linking the user profiles between the chat and incident management has additional benefits. As alerts are acknowledged and responded to within the chat environment, the events are recorded within the incident management solution. A clear history describing who took each action is recorded for future reporting and analysis.

    While there are many things to consider when integrating incident management into a chat application, the benefits are clear. Response time, ability to collaborate, and team access to incident details are crucial factors for incident resolution.

    About the Author / Serhat Can

    Serhat Can is a Technical Evangelist for OpsGenie. He has contributed to different parts of OpsGenie as an engineer and now tries to spread the word by coding, writing and talking about DevOps. He is still a proud member of the on-call schedules. Follow him on Twitter and connect with him on LinkedIn.
  • How Cognitive Bias and ‘HumanOps’ Affect Dev Teams

    How Cognitive Bias and ‘HumanOps’ Affect Dev Teams

    Does your team take into account how the human element can affect development practices? It’s often overlooked, but critical to consider. Jason Hand of VictorOps, devopsy.kinsta.cloud’s Top DevOps Evangelist for 2016, writes and speaks on this particular topic often. In fact, he will be delivering a keynote titled, “Cognitive Bias and Its Impact on Continuous Improvement,” at the upcoming SauceCon conference, to be held June 6-8 in San Francisco.

    SauceCon, the first-ever Sauce Labs user conference, is a three-day event filled with training, workshops, best practices and visionary content from the leading minds in automated testing.

    “Cognitive bias is an important topic that is often left out of the conversation. The ‘HumanOps’ side of DevOps is a fascinating area to explore and I’m excited to get the conversation going for those in attendance at SauceCon,” he said.

    Jason aims to help attendees understand the most important cognitive bias to watch out for, as well as ways to identify it in ourselves and others. Particularly when managing service disruptions and time-sensitive problems, understanding where we make common mistakes will go a long way to improving our response to outages, as well as continuously improving over time.

    Jason serves as a DevOps Champion and advisor at VictorOps, where he advises on the future functionality and direction of the on-call and incident management platform, counseling the team on modern DevOps principles and new methods of delivering reliable software at scale.

    In addition, Jason advises the growing worldwide community of IT professionals including Colorado’s front range, where he helps to organize DevOpsDays Rockies and the monthly DevOps meetups in Denver. Co-host of “The Community Pulse,” a podcast on building community within tech, Jason is dedicated to the latest trends in technology, sharing the lessons learned and helping people continuously improve.

    In 2016, Jason was named “DevOps Evangelist of the Year” by devopsy.kinsta.cloud. He is the author of two books on the subject of ChatOps and a forthcoming O’Reilly book on post-incident reviews, as well as a regular contributor of articles to Wired.com, TechBeacon.com and many other online publications.

    For more on upcoming SauceCon presentations or to register, visit the SauceCon website.

    About the Author / Rebecca Cramer

    Rebecca Cramer is a writer and communications strategist specializing in technology. With more than 20 years of experience across disciplines including marketing, internal and executive communications at companies such as Dell and Quest Software, Rebecca is passionate about creating and sharing good content of all kinds. In her spare time, she enjoys spending time at the beach and hiking in her native Southern California.

     

     

     

  • Webinar: Sandstorm or Significant: The evolving role of context in Incident Management

    RECORDING

    — Jules Louis

  • VictorOps Announces the Incident Automation Engine, Further Advancing Innovation in Real-Time Incident Management

     

    VictorOps helps companies bypass traditional Network Operations Centers by proactively routing alerts, transforming data, and solving problems using end-to-end automation

    BOULDER, Colo. – June 22, 2016 – VictorOps, the real-time incident management company for DevOps teams, announced the Incident Automation Engine, a set of cutting-edge features for on-call teams to automate their way to faster mean time to resolution(MTTR) through use of intelligent alerts, sophisticated routing, and smarter system outputs.

    Unlike other incident management tools that mainly focus on triaging alerts and notifications, the VictorOps Incident Automation Engine provides unsurpassed control and insight throughout the entire incident lifecycle via a combination of intelligent system inputs and actionable outputs. The Incident Automation Engine automatically quiets the noise of unnecessary alerts, delivers remediation solutions alongside alerts, and provides visibility into and documentation of all communications and actions that occurred during an incident. Additionally, through the use of outbound webhooks, the entire VictorOps solution can now be configured to send data to other tools in real-time, enabling users to do everything from automatically fixing standard issues to customizing dashboards.

    “More and more often, the best way to speed organizational innovation is by enabling developers to move quickly,” said Todd Vernon, VictorOps CEO and co-founder. “When it comes to a company’s uptime, this same concept applies. Today valuable time is lost with archaic alerting systems and manual processes. The [Incident Automation] Engine now becomes a foundation to automate out these inefficiencies, gain clearer access to actionable information and continuously evaluate and improve the inputs driving on-call processes.”

    Key features of the Incident Automation Engine include:

    • Alert Transformations– Quiet unactionable alerts and automatically route specific alerts to the correct team members.
    • Alert Annotations– Automatically append alerts with runbooks, monitoring graphs and other relevant information, giving the alert recipient immediate remediation steps.
    • Outbound Webhooks– Extend VictorOps platform data into other systems and integrate VictorOps incidents into other service dashboards.
    • API– Leverage the VictorOps API to extend VictorOps to existing legacy tools and reporting systems.
    • Post-Mortem Report Generator– Automatically pull a snapshot of all activities (alerts, conversations and remediation actions) associated with an outage. Easily use this data to report on SLAs and facilitate team retrospectives.

    VictorOps was one of five companies Gartner featured as a 2016 “Cool Vendor” in DevOps. The Incident Automation Engine is one of the many reasons for this recognition. Its purpose is to support on-call teams as they learn from each incident, providing them with the means to continuously improve and evolve their processes.

    “Visibility at velocity is very important to us so engineers know what needs to be addressed from problems identified in production,” said Mike Perttula, DevOps Specialist, Signiant. “[The] VictorOps Incident Automation Engine is allowing us to inform more team members in a timely fashion. We are lowering our MTTR and increasing the reach of our incident alerting audience without waking up everyone for the wrong reasons.”

    “With the Incident Automation Engine, our customers are now better empowered to resolve and even prevent future incidents, thereby protecting revenue loss, driving customer satisfaction, and maintaining brand reputation,” said Vernon.

    The functionality delivered as part of the Incident Automation Engine is now available in the Enterprise edition of the VictorOps product. For more information about the Incident Automation Engine, visit VictorOps.

    About VictorOps

    VictorOps is the real-time and agile incident management platform focusing on incident lifecycle management and collaboration for IT and DevOps teams. The solution combines the power of people and data to solve IT problems in real-time. The VictorOps platform seamlessly orchestrates team situational awareness, incident creation, escalation, notification, and remediation with team members regardless of physical location or time of day. Privately held, VictorOps is backed by Costanoa Venture Capital and Foundry Group. For more information, visit www.victorops.com and follow the company on Twitter @VictorOps.

  • VictorOps Enterprise Edition expanded with Incident Automation Engine

     

    VictorOps helps the most innovative companies bypass traditional Network Operations Centers in order to proactively ingest, transform, route, and solve problems using end-to-end automation.

    BOULDER, Colo. – June 22, 2016 – VictorOps, the real-time incident management company for DevOps teams, announced the Incident Automation Engine, a set of cutting-edge features for on-call teams to automate their way to faster MTTR through use of intelligent alerts, sophisticated routing, and smarter system outputs.

    Unlike other incident management tools that focus on triaging alerts and notifications, the VictorOps Incident Automation Engine offers a truly innovative combination making system inputs intelligent and relevant outputs fully actionable. The Engine automates human behavior in order to quiet the noise of unnecessary alerts, deliver real-time remediation solutions, and provide visibility and documentation into all communications and actions that took place during an incident. Additionally, through the use of outbound webhooks the entire VictorOps solution can now be configured to send information to other tools, take automatic actions, and sync with other alert sources and reporting systems already in place. The combination providing unsurpassed control and insight throughout the incident lifecycle.

    “With the Incident Automation Engine our customers are are now better empowered to resolve and even prevent future incidents, thereby protecting revenue loss, driving customer satisfaction and maintaining brand reputation,” said Todd Vernon, VictorOps CEO and co-founder. “More and more the best way to speed organizational innovation is through enabling developers to move quickly. When it comes to a company’s uptime this same concept applies. Today valuable time is lost with archaic alerting systems and manual processes. The Engine now becomes a foundation to automate out these inefficiencies, gain clearer access to actionable information and to continuously evaluate and improve the inputs driving on-call processes.”

    Key features of the Incident Automation Engine include:

    • Alert Transformations– Quiet unactionable alerts and automatically route specific alerts to the correct team members
    • Alert Annotations– Automatically append alerts with runbooks, monitoring graphs and other relevant information, giving the alert recipient immediate remediation steps
    • Outbound Webhooks– Extend VictorOps platform data into other systems and integrate VictorOps incidents into other service dashboards
    • API– Leverage the VictorOps API to extend VictorOps to existing legacy tools and reporting systems
    • Post-Mortem Report Generator – The ability to automatically pull a snapshot of all activities (alerts, conversations and remediation actions) associated with an outage. This information translates easily into SLA reporting and the facilitation of team retrospectives.

    Organizations of all sizes are increasingly looking to adopt incident management solutions in order to reduce the impacts of IT downtime. According to Gartner, the potential cost of downtime for organizations can approach $540K an hour. If reduced, mean time to resolution (MTTR) can prevent a modest 300 minutes of downtime in a single year, and businesses could save upwards of $2.5M.

    “Visibility at velocity is very important to us so engineers know what needs to be addressed from problems identified in production. [The] VictorOps Incident Automation Engine is allowing us to inform more team members in a timely fashion. We are lowering our MTTR and increasing the reach of our incident alerting audience without waking up everyone for the wrong reasons,” said Mike Perttula, DevOps Specialist at Signiant.

    For more information about the Incident Automation Engine, visit [URL].

    About VictorOps

    VictorOps is the real-time incident management platform focusing on incident lifecycle management and collaboration for IT and DevOps teams. The solution combines the power of people and data to solve IT problems in real-time. The VictorOps platform seamlessly orchestrates team situational awareness, incident creation, escalation, notification, and remediation with team members regardless of physical location or time of day. Privately held, VictorOps is backed by Costanoa Venture Capital and Foundry Group. For more information, visit www.victorops.com and follow the company on Twitter @VictorOps.

  • VictorOps Unveils Significant Mobile Application Enhancements to Cut Response Times and Reduce Burnout for On-Call Professionals

    Users can prepare, react to, and recover quicker from incidents using iOS and Android devices

    BOULDER, Colo. – March 30, 2016 – VictorOps, the real-time, agile incident management company for DevOps teams, today announced significant updates to the VictorOps mobile application. Since 2012, VictorOps’ immersive mobile applications alerts on-call teams to incidents and allows users to solve them quickly and seamlessly. VictorOps native, fully-functional mobile applications allow teams to remediate problems regardless of time of day or physical location. This increased mobility means that on-call teams are no longer tied to their desks, which keeps employee burnout to a minimum.

    Features of the upgraded version of VictorOps’ mobile application include:

    • Bi-directional chat integrations with Slack or HipChat which allows users to see system information and chat remediation data all in one application eliminating the need to toggle between applications
    • New in-app organization by team allowing users to quickly search through large organizations to coordinate with specific users to assist in incident remediation
    • New ‘quick filters’ that allow application users to differentiate between people currently online or using the application and those who are simply on-call
    • Ability to view alert annotations such as graphs or runbooks, to help the on-call professional determine the severity of the alarm
    • Highly customizable timeline that allows DevOps engineers to have full visibility into all of their systems or quickly zero in on recent conversations or alarms that pertain to them
    • Ability to launch a conference bridge within the mobile application and invite as many team members as are needed
    • Improved personal summary view that allows users to see when they are next on-call, any missed messages and other items that are pertinent to them

    “Each day thousands of our customers pull their mobile devices out of their pockets in order to respond and solve problems in real-time,” said Joni Klippert, Vice President, Product, VictorOps. “This latest version release will give hours of time back to on-call teams by providing everything they need to investigate, triage and communicate with other team members right from their mobile devices.”

    The latest version of the VictorOps mobile application for enterprises and SMBs is now available for download on the iTunes App Store or Google Play. For more information about the mobile application, click here.

    About VictorOps

    VictorOps is the real-time, agile incident management platform focusing on incident lifecycle management and collaboration for IT and DevOps teams. The solution combines the power of people and data to solve IT problems in real-time. The VictorOps platform seamlessly orchestrates team situational awareness, incident creation, escalation, notification, and remediation with team members regardless of physical location or time of day. Privately held, VictorOps is backed by Costanoa Venture Capital and Foundry Group. For more information, visit www.victorops.com and follow the company on Twitter @VictorOps.

  • VictorOps Announces DevOps Roadtrip to Impart Industry Best Practices Across the Country

    New event series provides practical tips for implementing and enhancing DevOps strategies

    BOULDER, Colo.–(BUSINESS WIRE)–VictorOps, the real-time, agile incident management company for DevOps teams, today announced its DevOps Roadtrip, a series of events designed to help software development and IT professionals across the country to better implement DevOps practices. The half-day events will focus on tactics and strategies to streamline processes specific to incident management and resolution.

    The first stop in Denver on March 29 will be held at Sports Authority Field at Mile High Stadium and will feature guest speakers from Forrester,Craftsy, and SendGrid. The half day event includes fast-paced TED style talks, topical breakout sessions, and a keynote presentation all aimed at helping others progress in their DevOps journeys.

    “DevOps can be an intimidating topic to many in IT. VictorOps wanted to create a welcoming forum where technology professionals can engage with DevOps experts in the industry,” said Jason Hand, DevOps Roadtrip MC and DevOps Evangelist, VictorOps. “Throughout the country, we’ll spotlight notable speakers in an effort to share DevOps wisdom amongst those tasked with the hard job of maintaining uptime. Our hope is that attendees can head back to their teams with actionable tactics to not only improve their organizations, but also simplify their own lives.”

    In addition to benefiting from a wide range of DevOps expertise and know-how, attendees will:

    • Hear real-life DevOps implementation stories from local companies
    • Learn about industry trends from renowned analysts
    • Network with others searching to implement real-time, agile incident management best practices
    • Have the opportunity to ask questions during an interactive Q&A session
    • And receive practical suggestions to take back to their teams

    By putting these teachings into practice, attendees can help their own companies become more efficient and ultimately more effective.

    “Organizations face an existential threat: deliver more value to customers faster than their competitors, or die. In the past, faster delivery usually meant lower quality and higher risk,” wrote Diego Lo Giudice and Kurt Bittner, Forrester Principal Analyst and DevOps Roadtrip Denver speaker in the December 2015 Forrester report entitled Agile and DevOps Adoption Drives Digital Business Success. “Leading organizations have shown how applying Agile and DevOps practices enables faster delivery with higher quality and lower risk.”

    Other stops on the 2016 DevOps Roadtrip include Seattle, San Francisco, Minneapolis, and New York.

    For more information about the DevOps Roadtrip, visit VictorOps.com/DevOps-Roadtrip, and to sign up for the Denver event, visitVictorOps.com/DevOps-Roadtrip-Denver.

    About VictorOps
    VictorOps is the real-time, agile incident management platform focusing on incident lifecycle management and collaboration for IT and DevOps teams. The solution combines the power of people and data to solve IT problems in real-time. The VictorOps platform seamlessly orchestrates team situational awareness, incident creation, escalation, notification, and remediation with team members regardless of physical location or time of day. Privately held, VictorOps is backed by Costanoa Venture Capital and Foundry Group. For more information, visit www.victorops.com and follow the company on Twitter @VictorOps.

    Contacts

    For VictorOps
    Mackenzie Kreitler, 978-518-4536
    victorops@matternow.com