Operations | Monitoring | ITSM | DevOps | Cloud

Compute functions that run on Amazon’s Elastic Container Service (ECS) require regular monitoring to ensure proper running and managing of containerized functions on AWS – in short, ECS monitoring is a must. ECS can manage containers with either EC2 or Fargate compute functions. While EC2 and Fargate are compute services, EC2 allows users to configure virtually every functional aspect. Fargate is more limited in its available settings but is simpler to set up.

In this blog post we’ll help answer the age old question, “What does this service talk to and what does it say?” We’ll see how to inspect inbound and outbound REST API calls to see what calls are being made and what incoming traffic causes a reaction. This can be pretty handy when you’re taking over maintenance of an existing service, or if your code just isn’t behaving the way you expect.

Grafana Tempo has had quite a year. Just eight months after it was announced at ObservabilityCON 2020, the open source tracing solution went GA. Since the Tempo team released v1.0 in June, we have ingested more than 39 trillion spans, a 26x increase from last year. We also introduced Grafana Enterprise Traces, which is powered by Tempo, to the Grafana Enterprise Stack.

Every day the world is changing in terms of technology. A new innovation happens every second, and software and websites are becoming more and more advanced. We can now access almost every service on the internet, and software needs to be maintained as a top priority so that customer service will not get hindered. Software monitoring, however, is not an easy task. It is a 24x7 business because any user can face an issue at any time.

As we step into another year, its time to reflect back on our most memorable moments & milestones that tell the story of Squadcast in 2021. 😇 The last 12 months have been nothing short of a spectacular journey for us as a company. We raised funding (Yaay!🙌), launched an open-source tool called SLO Tracker, helped organizations globally improve their reliability and made on-call shifts in general less stressful. Here’s how our year went by.

You have probably heard of Log4Shell, the security vulnerability that has ‘earned’ itself an NIST rank of 10: In this post I will show a really basic example of how this vulnerability actually works. I will walk you through some basic usage of the Log4J library and then show how some fairly basic inputs into this library can cause truly unexpected, and potentially disastrous, outcomes.

Most days at Cycle, we go through the day-to-day grind; checking tasks off our endless to-do list, looking forward, and striving towards our goals. We are focused on the small steps throughout each day: head down, working hard, placing one foot in front of the other. But every once in a while, it is necessary to pause, lift our head up, and look back at how far we have come. So, what have we been up to in 2021? We are always listening to user feedback and continuously seeking to improve our platform.

Silos in IT should be a construct of the past. Tight, rigid, and insulated IT silos were an unintentional design flaw of many IT organizations worldwide over the last few decades. Corporate teams would work on their respective piece of the puzzle in isolation, actively completing their tasks, but having little to no input or conversation on how their output contributed to the greater good. When you lay out the flow, it looks something like Figure 1.