v1.0.30

What's new in 1.0.30

• Cloud logs open in a log reader, not the table grid. A CloudWatch, Azure Monitor or Cloud Logging result used to land in the results grid, which gave a quarter of its width to the line and the rest to the stream name, the event id and the ingestion clock. It now opens as a stream of lines: the time, the level, and the line itself. The grid is one click away on the same footer toggle.
• A line's own noise comes off, and its payload opens in place. The timestamp most runtimes prefix is already the row's time column, and the request id is identical on every line of an invocation, so both move into the expansion along with the stream and any parsed fields. Click a line and whatever it was carrying unfolds underneath it, with embedded JSON pretty-printed and coloured. An ERROR or WARN colours its line and marks its left edge.
• The results search shows you why a line matched. It narrows the reader to matching lines and matches anywhere in an event, including inside a payload that is folded away. When the match is somewhere you cannot see, the line shows a fragment from around it instead of looking like it does not match, and the term is highlighted in the line, the chips, the prose and the payload.
• Azure Monitor and Cloud Logging read properly too. Those services write a whole record where CloudWatch writes a line. The reader composes those into a readable line, the record's own message first and its other fields after, instead of a wall of JSON on every row.
• A log result says when it looked. A log query is always bounded, and a statement with no time bound gets the last hour, which used to be invisible: a query over a busy log group came back empty and read as broken. The footer now carries the range as a control that re-runs the statement over a longer one, beside how much was scanned and whether a cap cut it short, and an empty result offers to look further back.
• A connection can name its log groups. Listing log groups is its own cloud permission, and a credential scoped to just the groups a team owns could read every event and still not connect. Name them on the connection and nothing needs to enumerate. Left empty, which is the normal case, nothing changes.
• On macOS, "Restart & Update" says what restarting will actually install. If a newer release was published while the toast was already waiting, the app used to sit on "downloading" forever while the staged version was the older one.

Install

Windows

Download SnoutData-Setup-1.0.30.exe below and run it. If SmartScreen shows a
red warning on first install, click More info → Run anyway. Updates install
themselves from inside the app after that.

Linux (Ubuntu / Debian)

Download and install the .deb:

wget https://github.com/snoutdata/app/releases/download/v1.0.30/snoutdata_1.0.30_amd64.deb
sudo apt install ./snoutdata_1.0.30_amd64.deb

Or add the apt repo directly (no download, pulls the latest):

curl -fsSL https://apt.snoutdata.com/snoutdata-archive-keyring.gpg \
  | sudo tee /usr/share/keyrings/snoutdata-archive-keyring.gpg >/dev/null
sudo tee /etc/apt/sources.list.d/snoutdata.sources >/dev/null <<'APT'
Types: deb
URIs: https://apt.snoutdata.com
Suites: stable
Components: main
Architectures: amd64
Signed-By: /usr/share/keyrings/snoutdata-archive-keyring.gpg
APT
sudo apt update && sudo apt install snoutdata

Both wire the same signed apt repo, so future releases install with sudo apt upgrade (or
automatically via unattended-upgrades), no re-downloading. Launch SnoutData from your app
menu (or run snoutdata); sign-in and the Chromium sandbox work with no extra flags.