Operations | Monitoring | ITSM | DevOps | Cloud

If you have some experience setting up monitoring for different setups, this post is for you. Since different parts of your architecture have different tasks, they also have different expectations. Today, we’ll take a quick dive into how to deal with that reality and set up monitoring for it. Warning: In this post, you’ll have to bear with our enthusiasm for setting things up perfectly.

The coronavirus (COVID-19) pandemic has forced many organizations to take unprecedented steps towards remote working. As a fully distributed team, we’ve faced the common challenges of remote work. Based on our experience from our very beginning in 2018, all but a few of these organizations new to remote working will face hurdles to overcome and may try to revert to colocation as soon as possible. Remote working is hard, even when it’s carefully planned and executed.

Have you heard about using the hash ring in Loki and Cortex? Here is a short version: In Cortex and Loki, the ring is a space divided by tokens into smaller segments. Each segment belongs to a single “ingester” (component in Cortex and Loki that receives data) and is used to shard series/logs across multiple ingesters. In addition to the tokens, each ingester also has an entry with its ID, address, and the latest heartbeat timestamp updated periodically.

When you deploy a new Rails app, you typically face a double-bind. If you use an easy platform like Heroku, you could create problems for yourself as your application scales. If you use a more fully-featured platform, you risk wasting time on ops that could be spent on your product. What if you could have both: an easy deployment option that is easy to scale?

COVID-19 is and will be the talk of the town due to its large-scale social, humanitarian and economic repercussions, but how can it affect a company’s systems? Many employers find themselves in the need to offer their employees remote working options, which means leaving the offices empty without actual machine supervision, which calls for a remote monitoring software to monitor their systems.

Distributed tracing is great — it helps you identify (micro)services within complex architectures having issues interfering with user experience, such as high latency or errors. But once a problematic service is identified, it can be difficult to find out which methods are to blame for the slowdown. Well, we have some big news to share for our Elastic APM users within the Java ecosystem.

The duality of observability is controllability. Observability is the ability to infer the internal state of a "machine” from externally exposed signals. Controllability is the ability to control input to direct the internal state to the desired outcome. We need both in today's cloud native world. Quite often we find that observability is presented as the desired end state. Yet, in modern computing environments, this isn’t really true.

We are thrilled to let you know that Uptrends is now certified ISO 27001 compliant. The ISO (International Organization Standardization) sets security requirements that a company must meet before an accredited auditor can grant the certification. If you’re familiar with the certification process, you know that it takes a considerable amount of time and work; however, the benefits that it brings for our company and our clients are worth the effort. Let’s take a look.