Latest news about Bitcoin and all cryptocurrencies. Your daily crypto news habit.
Why we built a gateway for cloud logs
Today, we’re introducing Logbird. A service to filter log streams for events and trigger activity for those events. This will enable developers to easily catch any event from logs, visualise it and notify other applications. It will become easy to find technical issues in distributed applications, track business events, automate workflows or even communicate between applications in an asynchronous manner.
First use case: error detection
Logbird is built by the team behind Dashbird — a serverless monitoring platform with over 250k Lambda functions under monitoring. One of the most common problems for developers building serverless applications have is tracking failures for managed services. Logbird addresses this by making cloud error detection simple. You can stream logs from services such as Lambda, API Gateway, AppSync, Fargate, and others, filter them for failures and get notified whenever a problem occurs.
Here’s a filter to catch all errors from Lambda functions (running Node.js).
But what if you could communicate using logs?
Gathering data on user activities/business events takes place in different parts of your application and can be complicated plus involve a lot of communication between different analytics services. With Logbird, developers can log out events in JSON format and gather everything in one place, where it is easy for business people to track and send events to external services. Dashbird uses Logbird to track signups, payments and other activities of clients and automates communications with sales and marketing tools.
Logbird sending information to slack for each signup.
A new event source
In a world of hybrid applications, part serverless — part container/VM/other, orchestrating workflows between the old and new can be complicated. Logs, however, propose an interesting opportunity to start execution flows by simply logging out a keyword or a command. As Logbird supports extracting data from log lines, a developer could even build asynchronous data-insertion flows that make database requests on the background. The rest is up to your imagination and use cases.
How does it work?
A key difference between analytics services is that Logbird can allow cheaper processing since it does not have to retain the original logs.
Logbird supports log intake by automatically integrating with AWS CloudWatch and by an HTTP endpoint which you can send logs with services such as FluentD.
For filtering, Logbird has developed its own query language (inspired by SumoLogic’s Query Language) but supports regular expressions, glob patterns and plain word matching as well. To make it easy to track known cloud events, we are starting a public filter library that is open for contributions by the community.
Logbird currently supports SNS triggers.
Available today
We’ve been using Logbird ourselves and worked with a handful of companies, guiding them to success. Today, we’re opening it up for the world in a beta format and you can sign up here. Also, check out our filter library and feel free to make contributions to it here.
Introducing Logbird — log gateway for the cloud was originally published in Hacker Noon on Medium, where people are continuing the conversation by highlighting and responding to this story.
Disclaimer
The views and opinions expressed in this article are solely those of the authors and do not reflect the views of Bitcoin Insider. Every investment and trading move involves risk - this is especially true for cryptocurrencies given their volatility. We strongly advise our readers to conduct their own research when making a decision.