Home / Companies / PagerDuty / Blog / January 2015

January 2015 Summaries

4 posts from PagerDuty

Filter
Month: Year:
Post Summaries Back to Blog
Adopting a DevOps model is crucial for enhancing collaboration and efficiency between development and operations teams, ultimately leading to a better customer experience and higher team satisfaction. Traditionally, developers and operations have worked in silos, causing delays and ownership issues, but DevOps encourages shared responsibility, faster development, and customer-focused goals. Transitioning to this model can be challenging due to entrenched silos and resistance to change, but focusing on existing successful collaborations and identifying key improvement opportunities can facilitate the shift. Creating a detailed plan with realistic timelines and involving key stakeholders is essential, as is being open to feedback and adapting plans based on initial outcomes. Measuring progress and conducting retrospectives after achieving milestones allows teams to reflect, celebrate successes, and iterate on processes for future improvement. Despite the challenges, the benefits of adopting DevOps, including improved product quality, faster development cycles, and enhanced team morale, make it a worthwhile endeavor.
Jan 22, 2015 1,103 words in the original blog post.
PagerDuty is designed to ensure timely notifications reach the right individuals during system failures by leveraging a robust alerting pipeline that utilizes distributed technologies for redundancy and fault tolerance. The pipeline begins with an event endpoint and involves several services, culminating in a messaging service that alerts people, relying on technologies like Scala, Cassandra, and Zookeeper. Cassandra has been used in production for over two years, with a relatively small dataset that is purged after events are resolved, and is configured in clusters across multiple datacenters to ensure durability and availability through a quorum consistency level. The cluster design, though atypical due to inter-datacenter latency, prioritizes durability and prevents data loss even if a datacenter fails, and the system is rigorously tested with intentional failures to ensure resilience. PagerDuty is actively seeking to enhance its infrastructure and is hiring for positions in San Francisco and Toronto.
Jan 20, 2015 556 words in the original blog post.
ChatOps, a practice that enhances collaboration and communication within organizations, is explored in this series, with a focus on enhancing bots through plugins to automate tasks. PagerDuty uses Ruby-based Lita and the chat bot Officer URL, integrating plugins such as lita-dig and lita-whois for DNS and whois records, lita-locker for resource management, and lita-github for streamlined GitHub interactions. These plugins help automate daily tasks, prevent accidental resource conflicts, and improve onboarding by providing a self-service dictionary with lita-wtf. The lita-enhance plugin enriches chat content by converting technical identifiers into more understandable information, while lita-status centralizes internal status updates to streamline incident response. These tools have bolstered productivity and scalability at PagerDuty, and the company aims to share its innovations by open-sourcing many of its internal developments. The next installment in the series will delve into the company's deployment and schema migration practices with their tool Igor.
Jan 13, 2015 714 words in the original blog post.
DevOps is not merely a job title but a philosophy and set of practices emphasizing collaboration, open communication, and the seamless integration of development and operations teams. It aims to enhance the efficiency and accountability of engineering and IT teams by fostering a culture that encourages testing, iterating, and problem-solving without assigning blame. The concept, which originated from Agile Systems Admin and Enterprise Systems Management movements, gained prominence for its ability to help organizations rapidly adapt to market changes and deliver superior software products. Patrick Debois and Andrew "Clay" Shafer first coined the term in 2009, and it gained momentum with the first DevOps Days event in Ghent, Belgium. Misinterpreting DevOps as a specific role can lead to organizational silos and reduced collaboration, while a proper understanding of DevOps principles can help integrate these practices into a company's culture, ultimately improving the delivery of products and services.
Jan 08, 2015 729 words in the original blog post.