Thu May 11 2023
Invocations View
Easily view all the Lambda function invocations that match a query. In addition to raw events, traces, and visualizations, this new feature provides you with a complete picture of your serverless functions.
Error Aggregation
Easily view all the errors for each service or Lambda function on a single screen. Errors are automatically grouped using vector distances so you can identify and resolve issues faster.
Service Health
With the new Service Health screen, you can get an at-a-glance view of your serverless services’ health. It includes key metrics like the number of invocations, number of errors, cold starts, number of alerts triggered, p99 latency and cold starts.
Multi-account and multi-environment support
You can now use our observability solution across multiple accounts and environments. This feature provides flexibility and scalability, allowing you to manage your serverless infrastructure more efficiently.
Simplified AWS Account Connection
With the simplified steps to connecting your AWS account, you can start running queries on your telemetry data with just a few clicks. We securely connect to your account through CloudFormation, and we keep you informed of the status of the integration at all times in the console.
Improvements & Fixes
- Improved the reliability of our ingestion pipelines
- Improved the quality of Baselime AI answers with better prompt engineering
- Improved latency of the Baselime query engine, you should expect 40% faster queries
- Changed the URL of the charts displayed in Slack alerts
- Changed the URLs used to query telemetry data
- Simplified the dashboard schema
- Removed the namespaces command in the Baselime CLI
- Made the frequency and window optional when defining an alert, with default values 1 hour.
- Enabled the baselime pull command to clone existing and discovered services
- Added filters and calculations
- COUNT_DISTINCT
- STDDEV
- VARIANCE
- DOES_NOT_INCLUDE
- MATCH_REGEX
- Added calculation alias to queries
- Fixed timezone mismatch when selecting a timeframe from charts
- Added individual pages for invocations
- Added sorting to services and functions tables
- Removed the “Discovered” on discovered services
Fri Mar 10 2023
TL;DR
- ✨ Dashboards ✨
- We shipped service discovery in preview
- We added 40+ example queries to help you answer common questions about your serverless architecture
- A considerable amount of effort went into reliability đź’»
- We improved Slack alerts
- We simplified the query and visual builders
- 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 so you never miss anything.
💯 What’s New?
Dashboards
Dashboards are the easiest way to share a collection of queries with your team, and the first step to help you achieve two of your main goals:
- quickly answer the question “are my systems healthy?”
- put together a set of queries for post-mortems or runbooks
The beauty of Baselime Dashboards is that you can add different views of a query to any dashboard. For example, you can add views for calculations, for events or for traces to your dashboard.
We also keep a history of dashboard views so you can keep track and go back to review the state of a dashboard at a specific point in time. You can even share it with your team!
Service Discovery Preview
Your serverless architecture is typically organised in multiple services and yet this context is lost in most observability solutions. This makes it difficult to query your telemetry data appropriately within the context of a service or set alerts for a single service.
So far, CloudFormation stacks could be used to manually set the boundaries of your services on Baselime.
We’ve launched automatic service discovery in preview to developers currently on Baselime. Automatic service discovery relies on your services being deployed using CloudFormation, it understands the deployment framework your team uses (CDK, Serverless Framework, SST, etc.) and can isolate telemetry data from each service at ingestion time.
When you run a query from within a service, you’re querying data for this service only. It’s fast, blazing fast.
For queries spanning multiple services, you can always query all the telemetry data across your architecture.
Query Examples
No more starting with a blank page. We’re building a library of common questions you might have about your serverless architecture. From slow queries to DynamoDB throttles, examples give you a starting point in understanding the emerging behaviour of your systems.
The query examples are open-sourced. Want to add a new set of examples? Let us know on Slack.
Reliability
We also have a distributed serverless architecture running on AWS, and as is the case for your team, reliability is always top of mind. We invested considerable amount of time in:
- Scalability of X-Ray traces ingestion
- Data replication for our ClickHouse clusters
- Disaster Recovery
And many more continuous improvement items…
Improved Slack alerts
A few things are important to know at first glance when you receive an alert:
- What is this alert?
- Where is it coming from?
- What values triggered it?
- How long has this been going on?
We improved our Slack alerts to provide all this information immediately, within Slack, without leaving your current context.
🎯 What’s Next?
- More templates and examples so you can get started with as little friction as possible
- Improved events table to facilitate navigating the results of a query.
- Service Discovery Beta launching for new developers on Baselime.
- Linked Metrics: currently, you can link your logs to your traces - how about your metrics?
👨‍💻 Hiring
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!
Thu Feb 02 2023
TL;DR
- 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.
XRay Traces
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.
OTel
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.
Observability Templates
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.
Our o11y templates are all open sourced and are accessible in our docs and on GitHub (Don’t forget to star us 🌟).
Web Console and CLI
Check out our new console and CLI. I’m sure you’ll like them - we’re looking forward to getting your feedback :)
Pricing Strategy
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.
👨‍💻 Hiring
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!