Operations | Monitoring | ITSM | DevOps | Cloud

2023 is coming to a close and the holiday season is here, but that doesn’t mean things at Gremlin are slowing down. In fact, we’ve released a ton of new features and improvements to make testing and improving reliability even easier. Now you can run Chaos Engineering experiments in serverless environments, create custom reliability test suites, create more flexible Scenarios, and more easily identify critical components in your environment.

Table of contents As a golden rule of building a developer tool, you should always dog-food your own product. But, how does this work with a monitoring solution 🤔? Doesn’t it create a chicken and egg problem? Checkly uses multiple tools to monitor the platform, and tools from our competitors as well. However, we still dogfood our platform heavily. I believe this is mainly due to our engineers also liking the product and finding it quite easy to monitor their features.

In this blog post, I take a look at modern IT governance by applying the classic “Three Ways” of DevOps principles originally introduced by Gene Kim in his seminal 2012 article. “We assert that the Three Ways describe the values and philosophies that frame the processes, procedures, practices of DevOps, as well as the prescriptive steps.” Here’s a quick reminder of the three ways set out by Gene: For Gene, all DevOps patterns can be derived from these three principles.

In today's digital-first landscape, maintaining the health and performance of your network is critical for the seamless operation of your business and its services. To that end, network observability has emerged as a key concept and discipline in ensuring the robustness and performance of networks. But what is network observability?

The adoption of AIOps monitoring technologies has been somewhat slower in EUC than many other areas of IT. The legacy VDI and DaaS vendor tools set expectations low for many. It is still relatively common for us to come across potential customers who are using legacy tools and manually exporting 6 months of data into an excel spreadsheet to try and work out average and peak usage of resources such as CPU to then manually calculate alert thresholds.

Are you relying on outdated manual methods to monitor your network? Struggling to keep up with the increasing complexity of your IT infrastructure? Being constantly reactive to network problems instead of proactive in preventing them? If you answered yes to any of these questions, then you’re putting your business at risk. But don’t worry, there’s a way out — Remote Network Monitoring.

Your IT Asset Management (ITAM) practice is not immune from the current corporate focus on IT optimization, that includes both asset utilization and ITAM operations. This, along with increasing technology complexities on the radar, are influencing many of the ITAM trends for 2024. So, where is everything heading towards?

Building provably reliable systems means building testable systems. Testing for failure conditions is the only way to reliably root out issues before they impact customers. However, most current Chaos Engineering and resilience testing is focused on the underlying infrastructure. This helps identify potentially catastrophic failures, but misses the more frequent failures that still significantly impact customer experience.

This is the fourth part of our 12-day Advent of Monitoring series. In this series, Checkly's engineers will share practical monitoring tips from their own experience. One challenge in conducting end-to-end (E2E) testing is managing the artifacts created during the process. These artifacts are necessary for asserting specific functionalities.