Operations | Monitoring | ITSM | DevOps | Cloud

StackState has always believed in the importance of open source and open standards, and we’ve demonstrated our commitment through ongoing support of open technologies. From the beginning, StackState supported StatsD and OpenMetrics. Even our agent is open source, designed to help organizations easily onboard our platform and to give them an extensible open way to observe their services. StackState is now proud to announce our next big open source step.

As a framework for goal-setting, the Objectives and Key Results (OKRs) methodology is an incredibly useful tool when implemented properly. It can help your engineering team better plan and stay aligned toward common objectives through the duration of the development process. On an individual level, OKRs can also encourage each team member to make personal progress toward their own goals or common team goals that would benefit the company.

In part 1 of the CLI Stands For…A CLI Into Series, we outline why you would want to use the CLI, some of the benefits of doing so, and a bit of CLI history and terminology. In part 2 – An Introduction to Shell Commands, get ready to roll up your sleeves and dive into a deeper understanding of the terminal.

When designing a solution, you should keep future needs in mind. If the number of users increases dramatically in a short period of time, the solution should be scalable enough to handle the new growth. Making systems scalable on cloud is relatively easier as compared to scaling on-premises infrastructure. AWS has provided excellent tools/services to enable your applications for as much scalability as you want.

From setting up new hires with everything they need to get to work to troubleshooting technical difficulties, IT teams often field the same kinds of requests over and over. And while each request might feel like a small task, collectively they can add up to a huge time sink in the long run.

Database backup protects your data by creating a copy of your database locally, or remotely on a backup server. This operation is often performed manually by database administrators. Like every other human-dependent activity, it is susceptible to errors and requires lots of time. Regularly scheduled backups go a long way to safeguarding your customers’ details in the case of operating system failure or security breach.

If you look back to the state of technology only a few decades ago, you’ll stumble upon a technological world full of silos and frustration. Two of an organization’s most vital teams—software development and IT operations—struggled to communicate effectively. Departments resided within silos, and development and testing were conducted at a snail’s pace.

Software engineering teams that adopt “as-code” practices, like using configuration files and automated workflows instead of manual configuration and tools, gain major improvements in velocity. But even companies that enjoy the success of as-code practices for development and delivery lag behind in applying them to operational concerns like monitoring and observability.

Observability is a new term that’s slowly entered the mainstream over the last two years. Today it’s used in the context of monitoring, but it’s much more than that. And it also goes way beyond visibility. So, in this blog, we set out to explore observability vs visibility and find out, what’s the difference? In a recent podcast, our friends at Riverbed neatly explained that seeing and observing are two different things, and can be compared to hearing vs listening.