Logbird allows services to communicate using logs.
It’s a channel for catching log events, analysing them and triggering activity. It offers a gateway to stream logs into and filter them for events. Events can be analyzed in the platform or used to trigger activity (SNS, Webhooks, Slack, Email etc). Logbird does not retain or index logs, making it cost-efficient and scalable for large-scale machine logs.
So what can I use it for?
The concept of a gateway can be applied to a wide range of use-cases. Below are some that inspired us to build Logbird.
Issue and event tracking for applications.
Modern applications, often built on managed (or at least hybrid) infrastructures, expand over multiple cloud services (AWS Lambda, Appsync, ECS, API Gateway, Aurora etc.) Usin log analytics for monitorign would get expensive at scale and be quite hard to set up since it requires knowhow. With Logbird, you could set community-managed filters to all clod service logs and track the failure events. Check out our list of ready-made filters.
Move data between services.
Tracking user activity and sending events to sales and marketing tools demands development time. Using Logbird, the developer can automate communication between different services by logging out the event data and forwarding it with Logbird. In Logbird, it’s easy for business people to run analytics and decide themselves of what to do with the data. For instance, they could send it to Zapier with a webhook, or log it out with Slack or send an email instead.
Alternative execution flow.
Logbird could be used to trigger code executions asynchronously. Instead of starting a process during the execution, log out a line that can be processed by Logbird and triggered an event for.
Build a data pipeline.
Downstream data entry can make batch operations easier and reduce load to databases and speed up the execution by reducing requests. You can use Logbird to extract JSON data from logs and insert it to data sources asynchronously.
How it works?
Currently, Logbird integrates automatically with CloudWatch and also provides HTTP endpoints to ingest logs. For event matching, Logbird has it’s own query language which is mainly inspired by SumoLogic’s query language. In addition, Logbird supports regular expressions, glob patterns and simple word matching. After the event is matched, you can look at the matched events from the platform and set triggers for caught events to