Dovydas Bykovas4 min read

Oxynote v0.10: Logs Join Metrics

Live logs come to your pages, along with easier, safer data source connections and faster charts.

An operations dashboard in Oxynote with a bookings chart above live booking and webhook logs and a webhook success gauge

Oxynote v0.10 is out, and it's one of our biggest updates yet. Metrics are now joined by logs, which brings Oxynote a step closer to a full observability suite. A page can show live logs from Loki right next to the charts and the notes that explain them.

Logs aren't the only addition. Connecting your data got easier and safer too: Supabase now has its own data source, and every data source can trust a certificate authority you run yourself. Once connected, charts load faster and ask much less of your databases. Before we get into the details, a few words about the people who made this release happen.

The Community Is Growing

Oxynote passed 500 stars on GitHub. Since v0.9.3, 12 people outside the team have sent more than 20 pull requests, from small fixes to features like pinned chart tooltips. Thank you to everyone who contributed. The release notes list each of them.

We also opened a Discord server, and more than 15 people have joined so far. It's the place to ask for help, share how you use Oxynote and tell us what you'd like to see next.

Everyone who wants to contribute is welcome, whatever the experience. We try to keep good first issues ready for anyone looking for a place to start. If you get stuck or want to talk through an idea before building it, we're happy to help on Discord.

Now, let's get into what's new in Oxynote.

Live Logs

Logs, like metrics, show how a system is doing. Metrics show the numbers, such as how many requests failed, whereas logs show the story behind them: which requests failed and why. When something goes wrong, they're often what tells you where to look and what to do next.

Until now, an Oxynote page could only show the metrics. Now it can show both. On any page, type / and choose Live Logs. Pick your Loki server, write a query, and the block shows the matching log lines as they arrive.

A Live Logs block on an on-call page, with a log volume chart above the newest lines and two charts belowPlatform logs and metrics on the on-call page

Some of the key features of the new Live Logs block:

  • Live updates: the block refreshes on its own, so the newest lines are always there.
  • Log volume: a chart above the lines shows how many logs came in over time, so a spike stands out.
  • Search and filter: search the lines, or narrow them down with LogQL. Click any field of a line to add it to the query as a filter.
  • Logs and metrics side by side: put a Live Logs block in a grid next to the charts for the same service.
  • Several queries in one block: such as one per service, merged by time.

The Live Logs editor with two LogQL queries, a log volume chart and a live preview of the matching linesTwo queries in one Live Logs block

Not running Loki yet? Every new workspace comes with Demo Logs, so you can try the block straight away. The assistant and AI agents connected over MCP can read your logs too.

Supabase

Supabase is one of the best-known platforms built on PostgreSQL. With v0.10, it gets its own data source instead of going through the PostgreSQL one. That mostly brings clarity and quality-of-life improvements. To connect it, open Settings, go to External Data Sources and click Connect next to Supabase.

The Connect Supabase form in Oxynote's settingsConnecting a Supabase project

The Help button next to each field now says where to find it in Supabase. Once connected, the query editor shows only your own tables, skipping Supabase's internal ones. Everything else works as it does for PostgreSQL: only a read-only user can connect, and queries use the same SQL, macros and variables.

From there, your app's tables can drive any chart on a page:

A bar chart of containers booked per day on each lane, from a Supabase projectContainers booked each day, read from Supabase

Your Own CA

Every data source can now use a CA certificate. If a data source has a certificate from your company's own certificate authority, paste that CA into the new field. Oxynote then always connects over TLS and trusts only certificates your CA signed.

Faster Charts

Until now, every chart opened a new connection to its data source and ran its own query, each time someone loaded the page. On a busy dashboard, that meant a lot of work for your database.

Oxynote now keeps its connections to each data source open and reuses them. It also remembers each answer for 10 seconds. When several people open the same dashboard at once, your database runs each query once, and everyone else gets the answer straight away.

Smaller Changes

  • Editing on phones and tablets works better with touch.
  • Hover the edit date at the top of a page to see who opened it and when.
  • Click a chart to pin its tooltip and scroll through every series.
  • Charts show when they're loading and why a query failed, instead of "No Data".
  • Changing a data source's URL clears its saved password, so it's never sent to a different server.

Along with these come fixes for invitations, chart reloading, SQL quoting and zoom on iPhones. The release notes list every change.

Wrapping Up

With logs next to metrics, a page can now tell a fuller story of a service: what the numbers say and what actually happened. To try it, pull the latest image and start a new container on the same volume. The install guide has the commands. A good first Live Logs block is the one for the service your team gets paged about most.

Oxynote is open source and runs as one Docker container: github.com/oxynote/oxynote. If something in v0.10 doesn't work the way you expected, we'd like to hear about it: ask on Discord or open an issue.