Watch patterns

Name the messages that matter, and hear about them.

A watch pattern is a phrase, or a regular expression, that Log Sentinel looks for in your logs.

You watch for
Payment authorization timed out
look back: 24 hours
summarize: yes
Teams chat: Store operations
Log Sentinel found
Oct 29, 13:31 UTC
Payment authorization timed out for order W261029005; retried and captured
Level
Error
Detail
PaymentGatewayException: the operation timed out after 30000 ms

Sent to the Store operations chat in Teams, with the full log entry a click away.

The problem

The warning was in the log all along.

In a B2B commerce stack, one misconfigured integration or unnoticed error can disrupt orders, confuse inventory or break a customer-facing workflow.

  1. Logs in too many places

    The store, the PIM and the ERP each keep their own logs, on their own servers and consoles.

  2. Nobody reads them

    Thousands of routine lines a day bury the one that says payments are timing out.

  3. Customers notice first

    A missing image or a failed shipping lookup is found when a buyer calls, not when it happens.

How it works

Collect, count, watch, tell.

  1. Collect

    Connect your online store, PIM and ERP, and their logs arrive in one place, each with its own view.

  2. Count

    Errors, warnings and info events for the last 24 hours, hour by hour, with the most common error messages.

  3. Watch

    Set the phrases or regular expressions that matter to you, each with how far back to look.

  4. Tell

    When a pattern matches, the right Teams chat hears about it, with a summary if you want one.

Logs

Every line, searchable, from every system.

Each source, such as the online store, PIM or ERP, has its own log: date, level and message, newest first, with warnings and errors highlighted. Search it, download it, or open any entry to see the full record.

  • The full entry: the complete record as the system logged it, including details such as the exception.
The Store Log: entries with date, level and message, such as product feed exports, customer sign-ins, sitemap regeneration and a price list synced from the ERP, with one warning highlighted about a copper price adjustment applied at checkout
The store log, with a warning about a price change on an item in a cart.
Log Details for one error: its date, source, level, the message that payment authorization timed out for order W261029005 and was retried and captured, and the full entry with a PaymentGatewayException after 30000 ms
One entry in full: what happened, and the exception behind it.
Watch patterns

You decide what’s worth an alert.

Add a pattern for each message your team should hear about: a payment timeout, a tax service error, a failed shipping lookup, or a product missing from the ERP feed. Turn patterns on and off as you need them.

  • Plain text or regular expressions, each with its own lookback window.
  • Summaries on request, and a Teams chat for each pattern.
  • Simulate a pattern from the settings page.
Log Sentinel watch patterns: payment authorization timed out, tax service returned 503, shipping rate lookup failed and not found in the ERP feed are enabled; slow request is disabled; each with a lookback and summarize setting, and New, Edit, Delete and Simulate buttons
Five watch patterns, four of them on.
The Pattern dialog: enabled, summarize, the signature Payment authorization timed out, not a regular expression, a 24-hour lookback and the Teams chat Store operations
A pattern for payment timeouts, sent to the Store operations chat.
Built to be trusted

Alerts about real problems, with the evidence attached.

Only what you ask for

Alerts come from the patterns you set, so routine lines stay in the log and out of your chat.

The original entry

Every message links back to the full log record, exactly as the system wrote it.

Counts you can check

Errors, warnings and info are counted over a stated period, with the hours they happened in.

Your logs only

Each company sees its own sources, logs and patterns.

Who it’s for

For teams who keep a commerce stack running.

Ecommerce operations

Hear about payment, tax and shipping errors as they happen, not when a buyer calls.

Integration owners

See the store, PIM and ERP logs side by side when a sync goes wrong.

Developers and support

Search the logs and open the full entry without signing in to each server.

FAQ

Common questions

Which systems can it collect logs from?

Your online store, PIM and ERP each get their own log. If you run other systems whose logs you want to see, tell us what they are.

How do alerts work?

You set watch patterns, plain phrases or regular expressions, each with a lookback window. When one matches, it posts to the Teams chat you chose, with a summary if you ask for one.

Will I get an alert for every error?

No. Only the patterns you set send alerts, and you can turn each one on or off. Everything else stays in the log and the overview.

Can I see the full log entry?

Yes. Open any line to see the complete record, including details such as the exception the system logged.

Let’s talk

Name the errors your team should never miss.

Tell us which systems you run and the problems you’ve heard about too late. We’ll show you how Log Sentinel would watch for them.