01 / GETTING STARTED

Help Centre

Signalsift collapses noisy logs into patterns. Paste text, get a frequency table of distinct events. Everything runs in your browser. Nothing is uploaded.

Using the tool

1. Paste

Open the App page and paste your log text into the textarea. Lines can be from journalctl, kubectl logs, a log file, or any terminal output.

2. Review

The tool automatically groups lines into patterns with counts. Sort by frequency (most common) or rarity (one-off lines). Filter by log level or search by substring.

3. Export

Download the grouped view as CSV or plain text to share, attach to a ticket, or open in a spreadsheet. Results disappear when you close the tab, so export what you need.

02 / FREQUENTLY ASKED QUESTIONS

What most people ask

Does Signalsift upload my log data to a server?

No. Signalsift runs entirely in your browser. The log text you paste is processed by JavaScript on the page, displayed in the results table, and discarded when you close the tab. No network requests are made after the initial page load. No data is uploaded, transmitted, or stored on any server. See the Privacy Policy for full details.

What log formats does it support?

Plain text logs in any format. The normaliser recognises and collapses fields that commonly cause false uniqueness:

TimestampsISO 8601, syslog (Jan 15 10:30:00), bracketed, Unix epoch seconds and milliseconds
IDs & addressesIPv4, IPv6, UUIDs, prefixed IDs (req_, txn_, sid_, corr_)
Values & pathsDurations (123ms, 0.5s), file paths, hex values, HTTP status codes, 4+ digit numbers

JSON and logfmt lines work as plain text — the normaliser operates on the rendered line, not on parsed structure.

How much log text can I paste?

There is no hard size limit. Very large pastes (500,000+ lines or multiple megabytes) may cause a brief pause in the browser while processing completes — the tool handles everything on the main thread. For genuinely enormous inputs, consider splitting into chunks. A Pro tier with Web Worker offload is planned but not yet built.

Why didn't my log lines collapse the way I expected?

The normaliser is regex-based and tuned for common log patterns. If a field uses an unusual format (custom ID prefix, non-standard timestamp, unconventional delimiters) it may not be recognised, and the lines will not group together. The normaliser is deliberately conservative — it prefers to keep two distinct patterns separate rather than falsely merging different events. If you have a specific example that does not normalise as expected, see the documentation on the App page for details on supported log formats.

Can I save my results or share them with a colleague?

Yes — use the CSV or Text export buttons to download the grouped view. There is no cloud save, no shareable link, and no account system. Export what you need before closing the tab, because state does not survive a page refresh or tab close. For sharing, attach the exported file to a ticket, chat, or email.

What is the privacy policy for pasting sensitive or classified logs?

Nothing leaves your machine. The tool is static JavaScript running entirely in your browser's memory. When you close the tab, both the paste and the results are gone. No server logs, no analytics, no third-party services receive your data. If your organisation's policy prohibits pasting into any website at all, you can audit the network tab in your browser's developer tools to confirm there are zero outbound requests after the initial page load.

03 / KNOWN LIMITATIONS

What Signalsift does not do (yet)

No schema parsing. Signalsift does not understand any specific vendor's log format. It collapses lines by statistical pattern, not by reading structured fields. If your log uses a completely custom schema, the normaliser may not recognise all variable fields.
No live streaming. It cannot tail journalctl -f, a cloud logging API, or a syslog server. Paste the text you have; it processes what is in the textarea.
No explanation or diagnosis. Signalsift counts and groups — it will not tell you what a message means, suggest a fix, or recommend an action. The analysis is yours.
No persistence. State does not survive a tab close or page refresh. There are no accounts, no saved history, no cloud sync. Export what you need before navigating away.
No large-file optimisation. Very large pastes run synchronously on the main thread. A Web Worker offload path is planned for the Pro tier but not yet built.
No live payment processing. Stripe is connected in test mode. No real card can be charged. Live billing is not yet set up.
No API or CLI. The tool is a web page only. There is no programmatic interface for automation. The open-source version is not separately licensed for redistribution at this time.

04 / CONTACT

How to reach us

Support channels are not yet available. See the documentation and FAQ on this page for help.

Self-service only

Support channels are not yet available for Signalsift. The FAQ and known limitations above cover the most common questions. If you have a question not answered here, check the Agen2ic website for product updates and contact information at the company level.

About this product

Check the FAQ above — your question may already be answered.
Signalsift is a product of Agen2ic, LLC, a Colorado limited liability company.
No postal address, phone number, or company registration number is published at this time.
We do not use live chat, phone support, or social media support channels.