Blog

We are excited to announce that Fylamynt is joining the Spot family at NetApp to continue our mission of Cloud Automation for Everyone!

Data aggregation is the process of combining data in a way that then presents itself into a more consumable and understandable form.

SysAdmin- System Administrator is one of the longest standing roles in technology. Learn how the evolution of the SysAdmin has matured through time

Incident management is the process that goes from an incident happening, to a ticket being created, identifying the issue and cause, remediating the service, and lastly reporting for post-mortems.

For this blog post, we will be using Squadcast as the example application for using the webhook trigger. With Squadcast, users can integrate with Fylamynt to accelerate Incident Response and Remediation.

As we head into 2022 and thankfully put a challenging 2021 behind us, we at Fylamynt are looking to the future and pondering what changes to the SRE (Site Reliability Engineering) ecosystem are likely to unfold.

Wow, hard to believe we are at the end of 2021! It’s been an evolving year of changes in more ways than one, and for us at Fylamynt as well. So as we approach this new year with renewed optimism, here’s a quick look back at how we’ve evolved to a modern cloud incident response platform to better serve SRE and DevOps engineers.

Often errors are requested to be fixed, and incidents require troubleshooting and might consume a lot of time before restoring the workflow process. This has caused companies to strengthen and enhance their incident responses towards these kinds of events by employing advanced technology and innovations. One of these is the automation of incident response.

We teamed up with Humio, a live observability platform empowering data aggregation, exploration, reporting, and analysis to create a new API integration for both platforms.

Here are the top 5 things you need to make a good runbook. Consistency: The same actions are taken every time. Accessibility: The runbook needs to be easily found and used by the response team. Automation: The runbook should automate the mundane and time consuming tasks. Observability: You need to record the inputs and outputs of every step for later analysis. Leveling Up: Based on the results (what you observed) the runbook should be dynamic and constantly improving.

No cloud service is perfect, and neither are the teams that work tirelessly to keep them running. They need modern tools and processes to respond quickly when things go wrong, and help ensure your customers continue to receive the value you provide.

This year at FinConDX our team has the honor of presenting a session entitled “Cloud Orchestration, Automation and Remediation (COAR) with Fylamynt” at on December 9th, 2021, and we want you to be there.

Today’s outage at Amazon Web Services' us-east-1 cloud region is impacting customers globally which results in the loss of revenue. These are not isolated incidents and can happen at any time and on any public cloud service provider. How do you deal with these outages? Do you maintain application-level high availability, do you wait for services to return to normal, or do you take manual action by means of failing over or migrating your workloads to a healthy region in order to retain uptime?

Have you seen payment processor uptime dramatically increasing? An up and coming online payment processor is taking aim at a market dominated by a few very large players.

It’s Time to Be an Incident Response Pro. You voted for it and now it’s here. Join us in this new incident response era.

Every company dreams of cloud operations running perfectly all the time, but the reality is there are constant issues, Incident Response Management & Remediation is the answer.

Attending AWS re:Invent in Las Vegas? If you’ve already registered to attend, have your flight booked and bags packed, you’ll want to add this event to your event checklist!

Performing repetitive tasks typically produces boredom, which can result in errors and mistakes. So today, let us try something new and challenge ourselves to get the job done more efficiently and be able to focus on the things that matter.

All of these services need to run continuously with no downtime. If the application isn’t working when a customer is hungry, they’ll switch to a competitor in seconds.

It’s not just the brick-and-mortar retailers that should worry about Black Friday this year. With increased online traffic, many DevOps teams will experience their busiest time of year as well.

When using cloud-native services, you will undoubtedly have cloud incidents that disrupt the normal operation of your systems. No SRE team believes they can achieve 100% uptime. Instead, they plan ahead, trying to anticipate what could go wrong (or has in the past) and create runbooks (sometimes called pipelines or workflows) to get things back to normal as quickly as possible.

AWS re:Invent is back and we want to see you there!

Site Reliability Engineering- the comprehensive explanation of this term was coined by google's prestigious engineering team when they realized that the duties and responsibilities required had deviated significantly from traditional IT/DevOps. One of the key differences is the use of code to help solve problems within cloud-native systems and infrastructure.

It seems the SRE world agrees that the I in IR stands for Incident, but what about the R?

Experienced DevOps personnel are very familiar with tools like Jenkins to create workflows and Terraform to automate orchestration. But are these the best tools to use when firefighting production cloud incidents?

Workflow as code simply means that we’re using code to orchestrate and execute a workflow, very likely in a distributed environment.

Global outages in AWS are rare, but AWS services experience intermittent problems nearly every day. You look at the AWS status page, and you see problems.

I’ll start in 1811 England. There was a new invention called a loom, allowing lower skilled laborers to operate and produce lower quality products that ruined the artisans’ reputation for quality. The name Luddites was coined, and this group of people went on to physically smash looms eventually causing Parliament to make frame-breaking a hanging offense.

Gone are those chill days, when an on-call person would take hours to fix a problem and restore the service for their customers. According to Statista, more than 50% of the enterprises reported they lost $500K or more per hour due to server downtime.

New to SRE? Learn the difference between Incident Response Vs Incident Management with Fylamynts team of experts

A runbook is not simply a sequence of steps, but may include logic (e.g. if-else, loops) and other constructs (e.g. wait for a resource). More precisely, a runbook is a workflow that is a directed acyclic graph (DAG) of actions.

At a high level an SRE is responsible for ensuring the systems run 24/7 and can handle scale as needed. To achieve this requires a lot of tools and expertise, not to mention often times having to “carry the pager” and handle incidents any time of the day or night.

SRE Vs DevOps- as these two phrases are used interchangeably, learn the core differences with the fylamynt team.

This year’s installment of KubeCon and CloudNativeCon looks to be the biggest yet, packing in over 200 sessions, 12 Cloud Native Tracks, and 70+ speakers in five days.

Facebook going down isn’t surprising and we have seen mishaps in the past. Just last month we noticed a similar DNS issue with Slack. The power of BGP is well known and it’s even surprising that this outage lasted so long and how widespread it really was.

We at Fylamynt are pleased to attend SaaStr 2021 and see old friends and new! SaaStr will be one of our first in person events where we have the opportunity to share our story with the industry.

Did you just receive a critical outage alert? Can you respond to it in just a few minutes?

As cloud computing is increasingly getting adopted all over, automation is taking a prime stage these days in the cloud-native space to streamline and manage various IT-related tasks. In this article, we will discuss cloud automation and various aspects related in brief.

Use the Fylamynt SlackOps feature for running automations and workflows without leaving your favorite Slack channel.

Analyzing and debugging workflows in Fylamynt

With Pulumi and Fylamynt’s low-code automation platform, you can easily customize your workflows on a secure platform to automate everyday tasks.

Approvals in the Fylamynt workflow

Being tethered to your laptop all day isn't a good sign. Schedule your workflows with Fylamynt and enjoy the flexibility of automating your cloud infrastructure processes.

Fylamynt can help you tap into that right brain creativity, with a visual and intuitive interface that makes automated workflow creation as easy as, well, drag and drop.

Streamline application traffic monitoring, and eliminate the need for constant human attention.

Using Terraform and Slack

If you use PagerDuty for incident management, this article is for you!

Today’s SaaS applications are constantly changing and require real-time observability. Instana is an automated Application Performance Management (APM) solution designed specifically for the challenges of managing microservices and cloud-native applications. Once you have observability, you want to act on the insights. You want to trigger a specific workflow based on what you find. In this article, you will learn how to do this by Fylamynt’s triggers built for Instana.

Manage your EKS cluster with various Fylamynt Actions

Our vision is to help engineers improve their productivity by codifying every part of their cloud workflow.

The clock strikes 2am and the dreaded pager rings for a DevOps engineer with a message titled "Prod API - too many 500 errors".

Understand the basics about Runbooks!

Introduction to "24 hours in the life of a DevOps Engineer"

Can we make Cloud Automation as simple as Scratch? Coding, testing and secure running of automation workflows with Fylamynt.