In our daily lives as developers, we have to deal with a lot of code that we did not write ourselves (or wrote ourselves but already forgot that we did). We use tons of libraries that make our lives easier because they deal with complex stuff like machine learning, time zones, or printing. As a result, much of the code base we work with on a daily basis is a black box to us. But there are times when we need to learn what is happening in that black box.
Rich content like videos and graphics used to cause network congestion and long load times when all the content was stored on a centrally located server. Fortunately, Content Delivery Networks (CDNs) came to the rescue in the late 1990s, letting users load rich content from a location geographically closer to them and reducing load times by distributing a cached version of content across servers worldwide.
Third-party APIs and cloud based software as a service (SaaS) tools have become a cornerstone of modern enterprises. It is essential to monitor log data and optimize API performance. This will ensure that development teams provide the desired advantages to clients and users. To address this challenge, businesses can use an observability pipeline. It is a set of tools and processes that monitor and analyze data from various sources. That includes third-party APIs and SaaS tools.
A core belief of Memfault is that we can ship faster when we have good infrastructure in place. An essential piece of this infrastructure is tools to send firmware updates over the air. It enables the team to ship more often and spend more time building features. In this article, we look specifically at what is required to ship over-the-air firmware updates for Linux systems. A good OTA setup should allow you to quickly prepare updates and ship them with confidence.
We believe monitoring should be set up as code and live in your repository. Today, we are thrilled to announce that our Checkly CLI is now available to everyone! The CLI is our native tool enabling monitoring as code (MaC). This is a significant achievement for us, and we owe it to our users who beta-tested the CLI and gave us valuable feedback over the past few weeks.
Incident response has been the cornerstone of reliability for decades. From digging in the server logs to navigating modern observability dashboards, responding quickly to incidents and outages is a big part of minimizing downtime. And it should be! When something breaks, your team should move as quickly as possible to address and repair the problem.
Data can be overwhelming. The purpose of this blog is help you sift through data to find exactly what you need to use it in a meaningful way when solving Citrix problems. After working in performance benchmarking and analysis, one thing I noticed is only the really really big companies have full-time staff dedicated to doing analysis on a daily basis. Which means, it’s up to the generalists, or Jacks and Jills-of-all-trades, to review data and make sense of it. How does one do this?
Flowmon is not a stand-alone system used in isolation. It is part of an ecosystem of monitoring and security tools used across the enterprise. Recently, we have introduced new integrations with Splunk and ServiceNow to simplify interoperability and enable IT and security teams to be more efficient. This is a good opportunity to remind of all the integration options and resources we have.