When a Solana program is live, its transactions tell a detailed story. An instruction can fail, an event can signal a large transfer, or a multisig can approve a change to the program. Finding the activity that matters, and knowing whether the monitoring pipeline itself is healthy, takes more than a stream of raw logs.
Microscope is an open-source, self-hosted monitoring and alerting tool for Solana programs. It decodes a program's instructions and events using its IDL, turns that activity into Grafana dashboards, and sends alerts to Slack, Telegram, or PagerDuty. It can also watch the Squads multisig that controls the program. The source code is available on GitHub under the MIT license.
From transactions to signals
Microscope reads confirmed transactions through a Yellowstone gRPC stream or a Solana RPC endpoint. Its indexer decodes the instructions and events associated with the program, then sends structured records to Loki and metrics to Prometheus. Grafana uses those records and metrics to show program activity over time and evaluate alert rules. One deployment monitors one program and, optionally, one Squads multisig.
That decoded data makes alerts more precise. A team can write a rule for a particular instruction or event, check a field such as an amount, and choose which channel receives the notification. A rule can also watch multisig actions, including proposal approvals. Alerts are based on decoded activity rather than matches against raw log text.
The dashboard gives teams another way to investigate. It shows transaction and instruction error rates, decoded instructions by type, recent program events, and multisig activity. If the datasource uses RPC polling, it also shows polling health. A failed on-chain instruction appears as program activity; it does not mean the indexer failed.
Know when the monitoring pipeline needs attention
An empty dashboard can mean a program is quiet, but it can also mean data has stopped flowing. Microscope includes health alerts for its own pipeline, covering conditions such as a stalled stream, stale RPC polls, a corrupt checkpoint, or records that are decoded but do not reach Loki. This helps teams check the monitoring system before drawing conclusions about the program.
Alerts carry a signal_kind label. Activity alerts identify an instruction, event, or multisig action; a datasource alert points to a problem with the monitoring pipeline. The project also includes a diagnosis workflow and an operations guide for working through incidents.
Get started with Microscope
Microscope can run as a Docker Compose stack on a machine or server, or on an AWS or GCP VM using Terraform. Teams with Grafana Cloud can connect the indexer and Alloy to an existing stack. The project also provides Kubernetes reference manifests for teams already operating their own observability infrastructure.
To configure a deployment, provide the program ID and IDL, choose a transaction source, and define the activity that should trigger alerts. A Squads multisig is optional. The repository includes a setup-deployment skill to help an AI agent prepare and validate the configuration, along with a Jupiter Lend walkthrough that demonstrates the stack with a sample set of alerts.
Explore the Microscope product page for the deployment options, dashboard examples, and a closer look at its alert configuration. The GitHub repository has the code and installation instructions.
