Product updates

Changelog

Follow what we’re building, improving, and shipping at OneMinute Logs.

Last updated Aug 18, 2026

Upcoming releases reflect our current plans and may change as the product evolves.

  1. In progressv1.2.0

    Structured logging

    Details

    We’re improving how OneMinute Logs understands and stores your application logs.

    Previously, a message such as “Payment failed” didn’t tell OML much by itself. With structured logging, the same message can include useful context automatically.

    This will make it easier to search logs, group similar problems, and build smarter alerts without requiring you to manually add all of this information.

    Before
    Payment failed
    With structured logging
    Payment failed
    Service checkout-api
    Environment production
    Provider Stripe
    Error card_declined

    What’s changing

    • Structured SDK logs following OpenTelemetry standardsDone
    • ClickHouse storage redesigned for structured logs at scaleDone
    • Automatic normalization and enrichment of incoming logsBuilding
    • Automatically group repeated errors and eventsNext
    • SDK
    • ·OpenTelemetry
    • ·ClickHouse
    • ·Logging
    Expected release · Aug 2026
  2. Upcomingv1.2.1

    Set up OML directly from your coding assistant

    Details

    The OneMinute Logs MCP server will give supported coding assistants everything they need to understand and set up OML in your application.

    Today, OML provides step-by-step AI setup prompts that you copy into your coding assistant. They can analyze your application, plan where logs should be added, and help configure OML one step at a time.

    With the MCP server, this becomes much more automatic. Your coding assistant will be able to access OML’s latest setup instructions, understand the available SDK features, and configure your application without requiring you to repeatedly copy prompts from our documentation.

    The MCP server will stay up to date as OML evolves. When we improve our SDKs, logging standards, or monitoring capabilities, your coding assistant can use the latest OML setup instead of relying on an old copied prompt.

    Current AI setup
    1. Open OML documentation
    2. Choose your framework
    3. Copy setup prompt
    4. Paste into coding assistant
    5. Review result
    6. Copy next prompt
    7. Repeat
    With OML MCP
    You: “Set up OneMinute Logs in this project.”
    ✓ Framework detected
    ✓ SDK configured
    ✓ Important events identified
    ✓ Structured logs added
    ✓ Monitoring configured
    ✓ Live Events added to your dashboard
    • MCP
    • ·SDK
    • ·Instrumentation
    • ·Developer tools
    Planned · Aug 2026
  3. Upcomingv1.3.0

    Group repeated problems

    Details

    Today, the same error can happen hundreds or thousands of times and appear as separate logs.

    OML will recognize when those logs are likely caused by the same underlying problem and group them together.

    This makes it much easier to understand how often a problem is happening without searching through thousands of nearly identical logs.

    Separate logs today
    Payment failed for user 128
    Payment failed for user 729
    Payment failed for user 1042
    Grouped in OML
    Payment failed
    ↳ 1,284 occurrences
    ↳ First seen 18 minutes ago
    ↳ Last seen 4 seconds ago
    • Errors
    • ·Fingerprinting
    • ·Alerts
    Planned · Aug 2026
  4. Upcomingv1.3.1

    Automatically spot unusual patterns

    Details

    OML will learn what normal activity looks like in your application and highlight meaningful changes.

    If the number of failed payments suddenly rises, OML can flag that change before you discover it manually while searching through logs.

    Normal activity
    ~10 failed payments / hour
    Unusual change
    87 failed payments / hour
    ↳ 8.7× higher than normal
    • Patterns
    • ·Monitoring
    • ·Alerts
    Planned · Sep 2026
  5. Upcomingv1.4.0

    Get alerted before you notice the problem

    Details

    OML will automatically create alerts when application behavior changes significantly — without requiring you to manually configure every threshold.

    Instead of waiting for someone to search the logs, OML can tell you when a familiar event suddenly happens far more often than normal.

    Normal behavior
    Payment failures
    ~8–12 / hour
    OML alert
    Payment failures: 74 / hour
    ↳ 6.4× higher than normal
    ↳ Started increasing 11 minutes ago
    • Alerts
    • ·Patterns
    • ·Monitoring
    Planned · Oct 2026
  6. Upcomingv1.5.0

    Ask questions about your application logs

    Details

    We’re adding a chat input directly inside the Live Events dashboard. You’ll be able to ask OML to find, compare, or analyze anything across your application logs using normal language.

    Instead of building a complex search or checking one service at a time, you can ask a question such as “Why did checkout errors increase?” OML will examine the relevant logs across your application and return a clear answer with the evidence it used.

    You can use it to investigate errors, understand changes after a deployment, compare environments, find activity for a user or request, and explore anything else recorded in your logs.

    Live Events chat
    Why did checkout errors increase?
    OML answer
    Checkout failures increased 7.2× at 14:32.
    Most failures come from POST /api/checkout.
    The increase started after the latest deployment.
    Likely cause: Stripe requests are timing out
    from checkout-service.
    Evidence
    • 1,284 related errors
    • 91% share the same fingerprint
    • First detected at 14:32
    • checkout-service is primarily affected
    • AI
    • ·Live Events
    • ·Search
    • ·Investigations
    Planned · Nov 2026