Operations | Monitoring | ITSM | DevOps | Cloud

Ever since the work from home (WFH) and study from home (SFH) initiatives became widespread due to the outbreak of COVID-19, there has been a huge effort among organizations to either set up new broadband connections or upgrade existing connections with higher bandwidth speeds. No matter the number of command centers an internet service provider (ISP) might have, keeping up with users’ demands—whether it’s about network speed or volume—can be a colossal undertaking.

Week after week, developers work tirelessly to publish updates that improve the stability of their mobile applications, so people like me can rely on our phones for work, play, and even occasional childcare. So to all those on a bug fix rotation right now: thank you. Unfortunately, my appreciation isn’t actually a great indicator of a release’s success. Developers are looking to Sentry to provide insights like version adoption, crash-free sessions, crash-free users, etc.

In some scenarios, you might want to have the possibility to get notified if all of a sudden, a large volume of alerts get raised inside Operations Manager. It could be that a large amount of alerts gets raised with low severity that usually isn't a problem on an individual occurrence. Maybe a VMware datastore latency alert is configured as a warning because they might fire off during backup windows. But what if all of the datastores all of a sudden indicates there is a latency issue and raises an alert.

We are delighted to announce the latest versions of our Azure and SCOM products. In this blog I’ll share the highlights of what’s new, including an update to Open Access which is now available in both Light and Dark themes! This unprecedented time has changed our ways of working at SquaredUp. Everyone has settled into the rigors of working from home and our Product Engineering teams have done an outstanding job with version 4.6.

Computing environments are constantly changing. Back when an on-premises server hosted your work, your infrastructure and applications were easy to track. Now that you’re developing in the cloud, things are more challenging. You’re learning that each team within your organization uses a different monitoring tool. At this point, you may be wondering if it’s time to build your own monitoring solution with open source tools at its core that everyone can use.

We will always remember April 2020 as the month that a DDoS attack took the world’s most expensive bottle of whiskey offline. We barely knew ye. Dateline: April 2020, the world’s most expensive whiskey auction is taken offline by DDoS. But other notable outages taught us a lot about which threats dominate our landscape. Namely DDoS attacks, which are highlighting vulnerabilities organizations have with redundancy and threat mitigation.

GrafanaCONline is live! We hope you’re able to catch the great online sessions we have planned over the next couple of weeks. If you haven’t had a chance to tune in lately, here’s what you missed on days 3 and 4 of the conference.

In today’s post, we’ll learn about Mnesia, see when you would use such a tool, and take a look at some of the pros and cons of using it. After covering the fundamentals of Mnesia, we’ll dive right into a sample application where we’ll build an Elixir application that uses Mnesia as its database. Let’s jump right in!

I’d like for you to think of your favorite app that you use almost every day. What do you use it for and why? Next, I’d like for you to think of the last time the app had a major design change that made you think, “What was the company thinking? Why would they change something that worked perfectly fine and make it so unusable? Did they not consult actual users before making this change?”

Hey there. Welcome to the fifth and final installment in our series on successfully deploying an app to AWS with the least effort. This week, we'll discuss things you need to worry about now that you've released, plus optimizing your app. Ok, so you've released your app. Congrats! However, we both know your work doesn't end here. You should continue improving your app, both on the end-user side and the back end.