Skip to content
Libra Logs

The AI logging service that understands your customers

Know which customers are failing, why, and how to fix it.

Your production logs, by customer. Libra reads every line, works out which customer it belongs to, and explains each failure in plain English with the log lines underneath.

Self-serve setup in one prompt: no sales call, no demo.

How it works

Follow one customer from a log line to a fix.

Meet Northwind, a fictional Example customer.

  1. Where it starts

    Thousands of log lines. Almost all of them fine.

    Somewhere in there, one customer's CRM updates have been failing since Tuesday. Nothing crashed, so nothing paged, and the failures disappear into the healthy traffic around them.

    Production logs, as they arriveExample
    INFOglobexGET /api/deals 200 38ms
    INFOinitechPOST /api/invoices 201
    ERRORnorthwindhubspot update rejected: software_used
    INFOumbrellaGET /api/inbox 200 21ms
    INFOhoolicalendar sync ok
    WARNglobexsalesforce: record locked
    INFOnorthwindGET /api/contacts 200 44ms
    ERRORnorthwindhubspot update rejected: software_used
    INFOvandelayPOST /api/signup 201
    ERRORinitechinvoice render timed out
    INFOumbrellaGET /api/threads 200 19ms
    ERRORnorthwindhubspot update rejected: software_used

  2. 01 · Spot

    Libra sorts every line by the customer it belongs to.

    Northwind rises to the top: its CRM updates are failing for 3 of its 8 people. The customers who are fine say so, in one word.

    CustomersExample

    Northwind

    CRM updates failing for 3 of 8 people since Tuesday.

    Globex

    Salesforce rejects edits to locked deals.

    Initech

    Invoice PDFs time out on large accounts.

    Umbrella

    No problems.

    Hooli

    No problems.

    Vandelay

    First logs arrived today.

  3. 02 · Understand

    Why it broke, in a sentence you can read.

    HubSpot rejects the update because the field is read-only on their side. The exact log lines sit right under the sentence, so you can check the claim yourself.

    Northwind · CRM updatesExample
    Needs attention3 of 8 people · since Tuesday

    HubSpot won't accept Northwind's contact updates. The software_used field is read-only on their side, so every save that touches it is rejected.

    The log lines behind it

    hubspot.contacts.update status=400 company=northwind
    error="Property software_used is read-only"
    retry 3/3 failed, contact left unchanged

  4. 03 · Fix

    Paste it into your coding agent.

    Copy the finding into Claude Code, Cursor or Codex. It arrives with its log lines, so the agent starts from the cause instead of a guess.

    claude · ~/appExample

    Pasted from Libra Logs

    Northwind: HubSpot rejects contact updates because software_used is read-only. 3 matching log lines attached.

    > find the cause and propose a fix

    syncContact() sends software_used on every update. HubSpot calculates that field, so stop writing it:

    src/crm/field-map.ts

    - software_used: contact.tools,

    + // software_used is calculated by HubSpot. Never write it.

  5. Every morning

    One briefing. Three customers need attention.

    Open the dashboard and the day starts with who needs you and why. Connect Slack and the same briefing lands in a channel.

    Briefing · Wednesday, 8:00Example

    3 customers need attention

    Everyone else is healthy.

    1. 01

      Northwind

      HubSpot rejects contact updates. software_used is read-only on their side.

    2. 02

      Globex

      A Salesforce validation rule locks deals, so edits never save.

    3. 03

      Initech

      Invoice PDFs time out for accounts with very long invoices.

    On your dashboard every morning. In Slack too, if you connect it.

  6. When it breaks

    Tagged in Slack when a customer breaks from their usual.

    Libra learns what normal looks like for each customer. When Northwind drifts far from it, the right person is tagged with the reason and a log line.

    #customer-healthExample

    Libra LogsAPP9:42 AM

    @maya Northwind just broke from its usual. Its CRM updates are failing far more than normal for this account: HubSpot rejects writes to software_used, a read-only field.

    hubspot.contacts.update status=400 company=northwind
    Open Northwind

  7. From your editor

    Ask your coding agent what's broken for Northwind.

    Connect Libra over MCP and your agent reads customer problems, searches logs and opens the evidence itself, with a read-only key.

    claude · ~/appExample

    > what's broken for Northwind?

    ● libra-logs · whats_broken

    One open problem. HubSpot rejects Northwind's contact updates because software_used is read-only on their side.

    It started Tuesday and affects 3 of their 8 people. Want me to trace where we write that field?

Production logs, as they arriveExample
INFOglobexGET /api/deals 200 38ms
INFOinitechPOST /api/invoices 201
ERRORnorthwindhubspot update rejected: software_used
INFOumbrellaGET /api/inbox 200 21ms
INFOhoolicalendar sync ok
WARNglobexsalesforce: record locked
INFOnorthwindGET /api/contacts 200 44ms
ERRORnorthwindhubspot update rejected: software_used
INFOvandelayPOST /api/signup 201
ERRORinitechinvoice render timed out
INFOumbrellaGET /api/threads 200 19ms
ERRORnorthwindhubspot update rejected: software_used

Northwind and every name here are fictional examples.

Self-serve setup in one prompt: no sales call, no demo.

Setup

Set up in one prompt.

Paste it into Claude Code, Cursor or Codex. Your agent runs the installer, you approve it in the browser, and nothing is pushed to your repo until you say yes.

Paste into Claude Code, Cursor, or Codex
Set up Libra Logs (https://libra.exla.ai/logs) in this repo.

1. From the repo root, run `npx -y libra-logs@latest --yes`. It waits for me to approve in the browser, so run it in the background or with a timeout of at least 10 minutes.
2. It prints a sign-in link and a code. Show them to me right away, then wait while I approve.
3. If it says it skipped the AI step, ask me whether Libra Logs may send this repo's source files to a model. Only if I say yes, rerun with `--ai-consent` added.
4. When it finishes, tell me the branch it created, what it changed, and whether my first log was confirmed. Do not push or open a PR unless I ask.
5. Then ask me whether to connect Libra Logs to you with `npx -y libra-logs@latest mcp add`, so you can search my logs and read change pages yourself.
Or run it yourself: npx libra-logs
Read the transcript

Libra Logs by Exla. Your logs know who's failing, and why. Now you do. Your customer updated their CRM. Some fields never saved. App logs and OTel, user and account context, and deploy and change context come together in Libra: customer activity, failed CRM fields, and evidence to check. See where things go wrong. Daily briefing: @Michael, heads up, some CRM fields aren't saving. HubSpot read-only fields. Salesforce locked records. Ask Libra follow-ups right in Slack. Use it directly through your coding agent. Spot. Understand. Fix. The AI logging service. Libra Logs. Built to understand your customers. Try for free. Self-serve setup in one prompt. exla.ai. The soundtrack is music and sound effects, with no spoken narration.

The context diagram and Slack-style card are designed examples of supported workflows, with customer identities omitted. The terminal is a real Claude Code session connected to a customer workspace through MCP. No raw logs or customer identities are shown.

Built to understand your customers.

Your production logs, by customer: who is failing, the reason in plain English, and a fix your coding agent can start from.