During Black Friday 2017 there seemed to be a lot of missing capacity in several AWS regions, even for on-demand instances. As such, some AWS users are wary of using EC2 spot instances going into Black Friday. In this post we will explain how Spot by NetApp can help ensure high availability while fully leveraging spot instances.
Every application has its unique compute infrastructure requirements. This is why container orchestrators such as Kubernetes provide application engineers with the use of taints and affinities to control precisely where pods run.
As the year draws to a close, we’ve got exciting news. In the new year, we will be launching SquaredUp version 5.0! So, what exactly is in this big, bold update, you ask? Expect a gorgeous new look and feel plus major improvements to our two most popular features – Open Access and Dashboard Designer. We’re also bringing you even more visualizations for your Web API integrations, so you can display data in the best possible way in your single pane of glass. The best part?
System Monitor (Sysmon) is Windows’ service for monitoring activity and recording it to the Windows event log. It is the go-to for logging anything on a PC. Sysmon will immediately log events, capturing vital info. The driver for Sysmon will install as a boot-start driver, enabling capture of any and all events from the get-go. Now, you can send Sysmon logs straight to Logz.io Cloud SIEM.
Log Sampling is a powerful feature introduced in HAProxy 2.0 that lets you define a percentage of your logs to create a representative view of your data allowing you to minimize your costs. Log files are the key to observability. They can provide helpful information that can be used for debugging as well as analytics that can be used to understand how users interact with an application.
Software companies large and small are embracing microservices as a superior approach to application development and management, compared to the earlier monolithic model. These software teams tend to reach out for containerization as their preferred way of packaging and shipping applications. Containers provide a lightweight encapsulation of any application, whether it is a traditional monolith or a modular microservice.
If your experience as a developer is anything like mine, the best moments are those known as the "flow state.” When distractions drift into the background and all your energy is going in the creative direction of solving the problem at hand. Your brain is directly connected to your users through your code. Months of progress happen in hours. Unfortunately, those moments are rare. But it’s not emails or Slack messages that are the biggest distractions.
Imagine you’ve been working on a new feature for weeks. Finally—after exhaustive QA and testing, and more late coding sessions than you care to count—you release with a feeling of both accomplishment and relief. Only to be woken up at 3am that something’s wrong. Or worse, you get flooded with customer complaints that it’s not working properly. Well, it’s probably a scenario you don’t need to imagine. Every developer has a version of this story to tell.
Error logs are the first port of call for any outage. Great error logs provide context and cause to a mysterious, 3am outage. Engineers often treat error logs as an afterthought. However, with some up front planning, error logs can become incredibly powerful. Let’s get right into it.
