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.

Customers can generate hosted status pages that display the status such as availability, response time and incidents of their services (websites, API, infrastructure) to their own clients or for internal use. All status pages are hosted and maintained by our care. Users point a custom domain to our DNS, and after seconds their page is ready. Hassle free.

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ī]).

Service Level Objectives, or SLOs, are an internal goal for the essential metrics of a service, such as uptime or response speed. We’re probably familiar with this definition, but what is the value of setting these goals? We’ll take a look at SLOs as both a powerful safety net and a tool to inform the allocation of engineering resources, while also considering the cultural learnings of SLO adoption.