Dropped log lines due to out-of-order timestamps can be a thing of the past! Allowing out-of-order writes has been one of the most-requested features for Loki, and we’re happy to announce that in the upcoming v2.4 release, the requirement to have log lines arrive in order by timestamp will be lifted. Simple configuration will allow out-of-order writes for Loki v2.4.
Keeping an eye on your site and sending you a notification when it goes down is one of the core features of Oh Dear. Under the hood, we'll send a request to your site and take a look if the response code is in the 200-299 range, which is the default response code range to indicate that everything is ok. Some of our users are monitoring password protected sites. In such cases, the web server might reply with status code 401 (unauthorised).
Robocalling is no small problem. These nuisance calls are the major source of consumer complaints, with some estimates suggesting that more than 22 billion robocalls have been made in 2021 alone – and we’re only halfway through the year.
The CPU attack is one of the most common attack types run by Gremlin users. CPU attacks let you consume CPU capacity on a host, container, Kubernetes resource, or service. This might sound like a trivial exercise, but consuming even small amounts of CPU can reveal unexpected behaviors on our systems. These behaviors can manifest as poor performance, unresponsiveness, or instability.
Mattermost v5.39 is generally available today and includes multiple bug fixes for increased stability (see changelog for more details).
Welcome to the Cloud 66 Changelog. These are the changes that have gone out this month.
This post will highlight and explain the importance of a pluggable data plane. But in order to do so, we first need an analogy. It’s time to talk about a brick garden wall! Imagine you have been asked to repair a brick garden wall, because one brick has cracked through in the summer sun. You have the equipment you need, so the size of the job will depend to a great extent on how easily the brick can be removed from the wall without interfering with all the ones around it. Good luck.
Delivering great performance and reliability for your critical applications just keeps getting harder, doesn’t it? Between microservices, mercurial cloud resources, containers spinning up and down, distributed teams, specialized teams, and developers making changes, it’s an increasingly complex environment. With so many moving parts, if something goes wrong, how do you know what happened where, and what your environment looked like at the precise moment the problem began?
