BT

InfoQ Homepage Logging Content on InfoQ

  • Facebook Open Sources LogDevice - a Distributed Data Store for Log Storage

    Facebook open sourced their internal distributed log storage project called LogDevice. It offers high write availability using replication, durable log storage and recovery from failure.

  • Understanding Production with DevOps Archeology

    Lee Fox spoke at Continuous Lifecycle London about tools and methods to help make sense of today’s complex systems and infrastructure; he calls it DevOps archeology.

  • Building Observable Distributed Systems

    Today's systems are more and more complex; microservices distributed over the network and scaling dynamically, resulting in many more ways of failure, ways we can't always predict. Investing in observability gives us the ability to ask questions to systems, things we never thought about before. Some of the tools that can be used for this are metrics, tracing, structured and correlated logging.

  • Microsoft Adds Application Insights Support for Azure Functions

    Microsoft recently announced an initial preview of Application Insights support for Azure Functions. As a result of this integration between the two services, developers now get built-in instrumentation for their code and a portal to view trends in their code’s performance. Developers are also able to set monitoring thresholds which can be used to create alerts or a callout to external webhooks.

  • Logz.io Offers Machine Learning Based Log Analysis

    Logz.io offers a hosted service which performs intelligent log analysis by using machine learning to derive insights from human interactions with log data that includes discussions on tech forums and public code repositories.

  • Five Ways to Not Mess Up Microservices in Production

    Alex Zhitnitsky of Takipi has written about five ways to try to improve the chances of successful deployed of microservices into production. As we will see, they share many similarities with other independent efforts, perhaps leading us to agreement on top areas of concern, if not ways of solving these problems.

  • How to Effectively Debug Software

    InfoQ interviewed Diomidis Spinellis, author of the books Code Reading and Code Quality, about finding and fixing errors in software, principles for debugging software and how to improve the effectiveness of debugging, how to write code that requires less debugging, and what managers can do to support error prevention and handling.

  • Log4j 2.6 Goes Garbage-Free

    Log4j, the popular logging library for Java, will include a number of configuration options that allows it to run in a completely garbage-free manner. The release follows previous attempts to improve the performance of logging libraries, and has been positively received by the industry. Further changes to increase the number of scenarios in which log4j can run garbage-free are expected.

  • DevOps Days Kiel Day 2

    Round up of the talks at DevOps Days Kiel's second day.

  • DistributedLog at Twitter for High Performance Logging

    Twitter is using replicated logs for high performance data collection and analysis of its systems. DistributedLog is the system developed at Twitter for this purpose. Twitter has developed a distributed key-value database, Manhattan. Manhattan can trade consistency for latency in reads following the eventually consistent data model. We examine Twitter's design and tradeoffs for DistributedLog.

  • The Transition to a New Log4j: a Q&A with Log4j’s Project Management Committee

    As recently published in InfoQ, the Apache Software Foundation announced the end of life of version 1 of Log4j, encouraging users to upgrade to version 2 of the popular logging framework. InfoQ reached out to the members of the Apache Logging Services Team to find out more about the transition to the new version of Log4j and about its future.

  • Log4j Version 1 Reaches End of Life

    Apache has announced the EOL of version 1 of Log4j. Although Log4j version 2 was released in July 2014, version 1 was maintained until early August 2015. The new version is a full rewrite of the logging library, addressing many of the issues of version 1 and achieving unprecedented performance. Apache has made an effort to ease the upgrade, although advanced users may need some migration work.

  • Newest NLog Improves Exception Logging, Adds JSON/Zip support

    NLog 4.0 has been released, and it brings improved exception logging, adds conditional logging, and support for JSON and Zip archives.

  • Amazon CloudWatch Supports JSON Logs and Integrates AWS CloudTrail

    Shortly after releasing the AWS CloudTrail Processing Library (CPL), Amazon Web Services has also integrated AWS CloudTrail with Amazon CloudWatch Logs to enable alarms and respective "notifications from CloudWatch, triggered by specific API activity captured by CloudTrail". The implied support for monitoring JSON-formatted logs has recently been officially released as well.

  • Amazon EC2 Gains Two-Minute Warning for Spot Instance Termination

    Amazon EC2 recently gained two-minute warnings before Spot Instances are reclaimed, a feature "formally known as a Spot Instance Termination Notice". The goal is to "allow more types of applications to benefit from the scale and low price of Spot Instances" by giving them time to save state, upload log files, or deregister from other components such as load balancers or cluster managers.

BT

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:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.