Operations | Monitoring | ITSM | DevOps | Cloud

Hiteshwar is an SRE based out of Mumbai, India. His area of specialization is in distributed systems. He works on Kubernetes, running his own custom clusters, maintaining them and creating tools to manage and monitor them. He likes to share his learnings by writing articles and blogs on Medium and Linkedin. He is an active speaker in meetups and developer groups and also teaches DevOps and SRE practices at learning centers.

Here’s a quick checklist to publish articles or guest posts on Fyipe Blog. We invite anyone to publish stories to any of our publications. If you wish to contribute. Please send an email to [email protected] with your draft article. Please make sure your draft article follows guidelines in this post. Here’s what all this means for you as a writer: Educate your readers and teach them something new. Cut all the fluff. Get to the point — fast. Do not waste their time.

The ever-growing complexity, scale and pace of IT environments puts a huge burden on IT Ops, NOC, and DevOps teams, who are tasked with keeping these environments up and running. One of the biggest challenges is Root Cause Analysis (RCA). When something breaks, they need to determine what broke it, and they need to do it fast.

If your end users regularly report issues before your Operations team discovers them, you need AIOps for earlier detection, faster action, and more precise diagnostics.

A lot of tech companies struggle with creating an effective and efficient on-call schedule internally for their product and service, this results in much longer downtimes when something goes wrong. They often over-burden their team members with repeated on-call duty which results in team member fatigue. Here’s how to create an on-call schedule that your team might love.

欢迎! [Huānyíng] In Mandarin, this means “welcome,” the first Chinese phrase I ever learned as a Mandarin Language Minor in college. It took me two weeks to understand the tonal variations, one week to memorize and properly execute the written stroke pattern, and another week to hone the ability to say it with confidence to my teacher (aka 老师 [Lǎoshī]).

Arild Jensen, SRE Manager at Upwork, talks about his journey into SRE and some best practices he picked up along the way including implementing a blameless culture, code review and making decisions based on hard data.

From open-sourcing our employee security training to sharing security best practices, PagerDuty is committed to contributing to the security community as a whole and considers security as a company-wide commitment. Our customers trust us to keep their data safe and secure. And on December 13, 2019, we took another step in embracing that trust by completing our SOC 2 Type 2 examination.