- Baselime is now in Public Beta, sign up today! ✨
- AWS X-Ray traces can now be queried in Baselime, and used for alerting
- We added support for OTel, send us your traces
- We shipped the fastest OTel tracer for Node.js Lambda functions - star us 🌟
- It’s possible to correlate your CloudWatch Logs and X-Ray traces in Baselime, with no code changes.
- We made a handful of observability templates to get you started
- We revamped our Web Console
- We simplified the vast majority of our CLI commands even further
- We have a new brand identity, we will be updating everything in the coming weeks
- Our detailed pricing strategy is now unveiled
- And much more…
We update our community on Slack as soon as any of these are in preview. Join the devs in our Slack community to never miss anything.
💯 What’s New?
Sign up to Baselime today here. Read on for what we shipped this month.
Baselime now automatically ingests traces from AWS X-Ray. You can now use your traces for queries and and alerts. A common use case is to alert on failed DynamoDB operations for example.
Moreover, you can correlate all your AWS Lambda logs with X-Ray traces, with no code changes. If the Lambda function is instrumented and sampled, you get this out of the box.
Yes, we know you want to use OpenTelemetry for your tracing, we got you covered.
Not only will we ingest your OTel traces, we are also building the fastest and most lightweight OTel tracer for Node.js Lambda functions. Drop us a star on Github!
Once in Baselime, your can explore your traces and use them as you would any other event in Baselime; set your configurations as code, run queries, define alerts, slice and dice in the CLI, etc.
For those who are not quite sure where to start with o11y for their serverless architectures, we’re building our public library of observability templates. With these, you can select the sort of services you’re building once your AWS account is connected to Baselime. Is it an API? Does it use SQS, or DynamoDB ? We’re building extensive templates to get the best-in-class observability on those services.
Pick your templates and start with the baseline observability you need. Once you’re more familiar with how things work, dive deep and slice and dice your data at will.
Web Console and CLI
Common question, quite a few people asked us how we would be charging for Baselime while we were in private beta.
Simple answer, we are as developer friendly as is viable. Firstly, we offer a generous free plan. Secondly, a usage-based plan on the number of events your architecture emits, with small increments to avoid unexpected such that you never get an unexpected bill. Moreover, if for some reason you were to go beyond the number of events you had planned for, simply let us know, we’ve been there and we’re always happy to work with you on these things.
New Brand Identity
To celebrate launching our public beta, we’ve revamped our brand identity. New logo, new website, all the good stuff.
Let us know what you think :).
🎯 What’s Next?
- More templates: The next month is all about providing you with more tools to get started with as little friction as possible
- More community activities: Our community has been focused on feedback over the past few months. We plan to make it a more vibrant community of serverless enthusiasts from all around the world; join us.
- Refining the platform: We’ve got a lot of the foundations for continuous observability covered. We want to spend the next month refining everything and streamlining the experience as much as possible.
We’re looking for an exceptional front-end developer to help us build the future of observability:
If this is you, the best time to join us was yesterday. The next best time is today!
We look forward to welcoming you in our Slack community. Let’s make Observability as Code the new norm!