InfoQ Homepage Observability Content on InfoQ


RSS Feed
  • Piercing the Fog: Observability Tools from the Future

    Visibility into those distributed systems and how they are performing is challenging. Despite all the observability tools available for site reliability, debugging remains incredibly difficult, and many SREs would agree that their debugging processes have only marginally improved. This article explores how observability for troubleshooting could be done from the user’s point of view.

  • Instrumenting the Network for Successful AIOps

    AIOps platforms empower IT teams to quickly find the root issues that originate in the network and disrupt running applications. AI/ML algorithms need access to high quality network data to determine what went wrong and where. Network visibility starts from TAPs around network equipment, and teams can add application instrumentation and logs as data sources for complete insights.

  • Load Testing APIs and Websites with Gatling: It’s Never Too Late to Get Started

    Conducting load tests against APIs and websites can both validate performance after a long stretch of development and get useful feedback from an app in order to increase its scaling capabilities and performance. Engineers should avoid creating “the cathedral” of load testing and end up with little time to improve performance overall. Write the simplest possible test and iterate from there.

  • Realtime APIs: Mike Amundsen on Designing for Speed and Observability

    In a recent apidays webinar, Mike Amundsen, trainer and author of the recent O’Reilly book “API Traffic Management 101”, presented “High Performing APIs: Architecting for Speed at Scale”. Drawing on recent research by IDC, he argued that organisations will have to drive systemic changes in order to meet the upcoming increased demand of consumption of business services via APIs.

  • Understandability: The Most Important Metric You’re Not Tracking

    Understandability is the concept that a system should be presented so that an engineer can easily comprehend it. The more understandable a system is, the easier it will be for engineers to change it in a predictable and safe manner. A system is understandable if it meets the following criteria: complete, concise, clear, and organized.

  • The Fundamental Truth behind Successful Development Practices: Software is Synthetic

    Software systems are creative compounds, emergent and generative; the product of complex interactions between people and technology. They are different from the orderly, analytic worlds that our school-age selves expect to find. Being so full of complexity and uncertainty, we use a different way to arrive at a solution.

  • Q&A with Tyler Treat on Microservice Observability

    Tyler Treat attempts to disambiguate the concepts of Observability and Monitoring. He discusses how the complexity of elastic systems produces more unknowns that require a discovery-based approach. InfoQ recently sat down with Treat to discuss the topics of observability and monitoring, and he shares some challenges and best practices when introducing observability concepts.

  • Sustainable Operations in Complex Systems with Production Excellence

    Successful long-term approaches to production ownership and DevOps require cultural change in the form of production excellence. Teams are more sustainable if they have well-defined measurements of reliability, the capability to debug new problems, a culture that fosters spreading knowledge, and a proactive approach to mitigating risk.

  • DevOps and Cloud InfoQ Trends Report - February 2019

    An overview of how the “cloud computing” and DevOps space is evolving in 2019 including updates on Kubernetes, Chaos Engineering, Service meshes and more.

  • Observability-Driven Development for Tackling the Great Unknown

    How does observability-driven development differ from monitoring? As our distributed systems become increasingly more complicated and as our silos break down for DevOps testing, automation, and efficiency, ODD arises as a superset of monitoring to understand your code’s unknown unknowns. Includes insights from Honeycomb Founder Charity Majors.

  • Microservices in a Post-Kubernetes Era

    How are microservices standing in the Kubernetes era? The microservice architecture is still the most popular architectural style for distributed systems. But Kubernetes and the cloud-native movement have redefined certain aspects of application design and development at scale.

  • Istio and the Future of Service Meshes

    A service mesh provides a transparent and language-independent way to flexibly and easily automate networking, security, and observation functions. This article examines the past, present and future of the Istio service mesh. The near-term goal is to launch Istio to 1.0, when the key features will all be in beta, including support for Hybrid environments.


Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.