steipete

Bslog

Name: Bslog
Author: steipete

Data community

SOURCE https://github.com/steipete/bslog

Description

cli for Better Stack to fetch logs, ClickHouse SQL style. Made for humans and agents.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

bslog - Better Stack Log CLI

[![npm version](https://img.shields.io/npm/v/@steipete/bslog.svg)](https://www.npmjs.com/package/@steipete/bslog) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![Bun Version](https://img.shields.io/badge/bun-%3E%3D1.0.0-000000.svg?style=flat&logo=bun)](https://bun.sh)

A powerful, intuitive CLI tool for querying Better Stack logs with GraphQL-inspired syntax. Query your logs naturally without memorizing complex SQL or API endpoints.

Features

GraphQL-inspired query syntax - Write queries that feel natural and are easy to remember
Simple commands - Common operations like tail, errors, search work out of the box
Smart filtering - Filter by level, subsystem, time ranges, or any JSON field
Beautiful output - Color-coded, formatted logs that are easy to read
Multiple formats - Export as JSON, CSV, or formatted tables
Fast - Built with Bun for maximum performance
Real-time following - Tail logs in real-time with -f flag
Query history - Saves your queries for quick re-use
Configurable - Set defaults for source, output format, and more
Responsive networking - Uses the native Fetch API with sane timeouts so hung connections never stall your session

Better Stack MCP vs bslog CLI

Better Stack's MCP (Model Context Protocol) endpoints expose the same log storage that bslog queries, but they serve different workflows. Reference the [official MCP integration guide](https://betterstack.com/docs/getting-started/integrations/mcp/) for setup, and use the two side by side:

Token footprint matters. The stock MCP ships ~50 tools and consumes roughly 7 k tokens of system context before it does any useful work. If you need lean prompts or run on constrained models, that overhead is noticeable.
Latency favors the CLI. bslog keeps a single HTTP session alive and streams JSON rows immediately; in practice a 5 0