If you’ve ever started a new job, you know what a whirlwind those first few days and weeks can feel like. A new job means meeting new faces, learning new processes, familiarizing yourself with new and unfamiliar technology, and discovering what new challenges you’ll be facing for the foreseeable future. It can all be quite overwhelming — particularly at companies that don’t offer top-of-the-line employee onboarding programs.
OpenStack has been around for a good while now, and many of us associate it with the period of IT technology’s initial transition from individual appliance implementation on hardware, to cloud compute and virtualisation. And yet in 2020 we cannot skip this topic when talking telco infrastructure. So how is OpenStack still pertinent to telco organisations, and what in broad terms is new and exciting or worth discussing today about OpenStack?
With 2020 dominated by a global pandemic, organizations expedited their digital transformation strategies. (According to TechFirst podcast, COVID19 accelerated digital transformation by an average of 6 years.) One of the most significant changes was the rapid move to a remote workforce. This required stopgap measures to keep the business running. While these measures met the company’s immediate needs, the measures also introduced anticipated and unanticipated issues.
2020 is behind us. But we are still reeling under its effects. The disruption at work due to Covid left companies to rethink their IT strategy and focus on digital experience monitoring for their vast remote workforce. However, in these unprecedented times, Exoprise successfully managed to deliver the best monitoring outcomes to its global customers.
Since 2018, Watchdog has provided automatic, machine learning-based anomaly detection to notify you of performance issues in your applications. Earlier this year, Watchdog started grouping APM anomalies across your services, allowing you to better understand the scope of the issue.
As an IT specialist, you should have an aptitude for all the essential tools vital for the efficient running of IT infrastructure. These software programs designed for their specific purposes basically serve the same purpose as an engineer’s toolkit. They make it easy to get the job done, and on top of that, get it done well. Depending on your job, you may or may not need to use all the tools. But as an IT professional, you should know which tool can help you with which task.
Here’s is a look back at the privacy-related changes and milestones of the Healthchecks.io website. If you also run a small SaaS, feel free to compare the notes. If you have suggestions or questions, please let me know!
With HAProxy, you can implement a circuit breaker to protect services from widespread failure. Martin Fowler, who is famous for being one of the Gang of Four authors who wrote Design Patterns: Elements of Reusable Object-Oriented Software, hosts a website where he catalogues software design patterns. He defines the Circuit Breaker pattern like this: The basic idea behind the circuit breaker is very simple. You wrap a protected function call in a circuit breaker object, which monitors for failures.
In my ongoing Loki how-to series, I have already shared all the best tips for creating fast filter queries that can filter terabytes of data in seconds. In this installment, I’ll reveal how to correctly escape special characters within a string in Loki’s LogQL. When writing LogQL queries, you may have realized that in multiple places you have to write strings delimited by double quotes.
This article was originally published on InfoQ at December 3rd 2020. If you’ve migrated from a monolith to a microservices architecture you probably experienced it: Modern systems today are far more complex to monitor. Microservices combined with containerized deployment results in highly dynamic systems with many moving parts across multiple layers.
