Practical overview
When it fits
Use Sologger when you have Solana RPC logs and want to structure them for program-level observability or transport them to a Logstash or OpenTelemetry endpoint.
Who it is for
- Solana developers who need structured logs for on-chain programs.
- Operators connecting Solana RPC logs to a Logstash or OpenTelemetry observability pipeline.
- Application developers who want libraries for extracting, structuring or exporting Solana logs.
Documented uses
- Parse raw Solana RPC logs into structured logs for specified program IDs.
- Extract logs from Solana API structures such as blocks, transactions and responses.
- Forward structured logs over TCP to Logstash or OpenTelemetry.
- Prepare a documented Compose configuration for monitoring chosen program IDs with Parseable or OpenSearch.
Requirements & limits
The repository specifies the Apache-2.0 license and links to a browser-based Sologger UI.
- The Logstash and OpenTelemetry transports are enabled through separate build features.
- The README recommends separate binaries if both Logstash and OpenTelemetry support are required.
- Sologger's default config path is
./config/local/sologger-config.json;SOLOGGER_APP_CONFIG_LOCcan override it. - The repository's Compose examples use program IDs in
sologger-config.jsonto select programs for monitoring.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build a Sologger binary for one transport
Build the binary with Logstash or OpenTelemetry transport enabled.
Before you start
- The Sologger source repository
- Rust Cargo
- Choose either Logstash or OpenTelemetry as the binary's transport
Steps
For Logstash transport, run the command below.
cargo build --features 'enable_logstash'For OpenTelemetry transport, run the command below.
cargo build --features 'enable_otel'
Expected outcome
A Sologger binary built with the selected transport feature.
Guide limitations
- The README says enabling both features in one build is possible but not recommended; it recommends building and running separate binaries when both destinations are needed.
- This guide covers building only; configuration and running the binary are separate steps.
Set up a Docker Compose example for program monitoring
Prepare a documented Sologger Compose example to monitor selected Solana program IDs with a log management system.
Before you start
- The Sologger repository's Docker Compose examples
- Program IDs for the Solana programs to monitor
Steps
Choose the repository's Parseable or OpenSearch Docker Compose example.
Update the program IDs in
sologger-config.jsonfor the programs to monitor.
Expected outcome
The example configuration is set to monitor the selected program IDs.
Guide limitations
- The documented steps cover selecting the example and editing program IDs, not starting the Compose services or confirming a running pipeline.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- brytelands/sologger · Official homepage title · retained in its source language

