Monoscope lets you ingest and explore your logs, traces and metrics. We store these in S3 compatible buckets. Query in natural language via LLMs. https://monoscope.tech
  • Haskell 59.1%
  • HTML 13.4%
  • TypeScript 12.2%
  • JavaScript 11.6%
  • PLpgSQL 1.5%
  • Other 2.2%
Find a file
Anthony Alaribe 14da1fd0e6 Clear the hlint backlog, including ten hints no edit could ever satisfy
`make lint` had been red for long enough that nobody read it. Ten of the thirty
findings were unsatisfiable: the `Control.Exception.fromException` rule also
matches the already-correct *unqualified* use, so it reported `Found:
fromException / Perhaps: fromException` once per call site. The file already
documented this exact trap for `displayException`, ending "if one starts
self-suggesting, delete it for the same reason" — `fromException` started when
the Slack retry paths began using it bare, so it goes for the stated reason.

The other twenty are real and applied by hand, since `hlint --refactor` cannot
run here (it looks for a GHC 8.10.7 that is not installed): six `pure () -> pass`,
two redundant `toStrict` under `decodeUtf8`, an explicit '0'..'9' range that is
`isDigit`, two `foldMap`/`<$>` fusions, a redundant `&` on a section,
`atomicModifyIORef'_`, Relude's `decodeUtf8'`, `fmap f $ x -> f <$> x`, a single
-constructor `data` -> `newtype`, two lambdas that eta-reduce, and a `do`
wrapping one statement.

Also drops two test statements that reset `apis.anomalies.acknowledged_at` /
`archived_at`. Nothing has written those columns since the mirror was retired,
so they were resetting state no code produces.

`hlint src` now reports no hints.
History 2026-09-11 18:08:52 +02:00
.githooks feat(pre-commit): add fourmolu hook for auto-formatting Haskell files (#385) 2026-05-17 22:58:00 +02:00
.github Ship the whole deploy locally, so CI stops being the critical path 2026-09-10 08:42:19 +02:00
.impeccable feat(service map): environment facet, via an additive table 2026-08-10 03:23:36 +02:00
app otel waterman 2025-04-04 01:25:58 +00:00
assets/demos docs(landing): storyboards for the product films 2026-08-12 12:13:31 +02:00
bench benchmark timefusion and improve billing page 2026-05-17 19:26:22 +02:00
ci Ship the whole deploy locally, so CI stops being the critical path 2026-09-10 08:42:19 +02:00
cli Support trace IDs in timestamped CLI lookups (#536) 2026-09-07 17:24:22 +02:00
config fix(ui): stop a deploy from silently breaking open tabs, and delete the dead service worker 2026-08-31 22:51:27 +02:00
docs Ship the whole deploy locally, so CI stops being the critical path 2026-09-10 08:42:19 +02:00
e2e Make the issue-tabs e2e test able to pass 2026-09-11 12:21:13 +02:00
hpack-includes feat(git): GitSpec's vendor fixtures, blob-cache follow-ups, and the staged view drop 2026-08-12 17:00:14 +02:00
npm Add ANSI-colored summary column rendering for CLI logs search (#340) 2026-03-15 02:48:58 +01:00
observability/monitors Reconcile local work, update monitor recipients and compact chart retry control 2026-09-07 15:28:42 +02:00
plans Record executed doctests for the runbook increment 2026-09-09 20:26:48 +02:00
proto/opentelemetry chore(otel): sync upstream proto to v1.10.0 2026-05-06 11:01:43 +02:00
scripts Ship the whole deploy locally, so CI stops being the critical path 2026-09-10 08:42:19 +02:00
shared Give each wire type's schema a home on the record it describes 2026-09-11 13:28:54 +02:00
src Clear the hlint backlog, including ten hints no edit could ever satisfy 2026-09-11 18:08:52 +02:00
static Address review: count firings not ticks, close the ack race, index the timeline 2026-09-11 14:47:02 +02:00
test Clear the hlint backlog, including ten hints no edit could ever satisfy 2026-09-11 18:08:52 +02:00
tests/golden feat(billing): bill the cycle Stripe bills, and link every invoice 2026-09-04 18:56:19 +02:00
web-components fix RUM behhaviors 2026-09-10 13:04:58 +02:00
.dockerignore Optimize CI: run tests in deps container, remove .git from Docker build 2026-03-08 13:05:30 +01:00
.editorconfig use widgets for explorer and implement event listening for filter element add and update queries 2025-03-03 03:47:41 +01:00
.env.example Ship the whole deploy locally, so CI stops being the critical path 2026-09-10 08:42:19 +02:00
.ghci perf(replay): sort merge files by first-event timestamp without materializing the array 2026-07-11 14:42:31 -07:00
.ghcid add .ghcid 2024-11-18 22:49:25 +01:00
.gitignore Fix empty team picker 400, KQL pipe suggestions, and make e2e reproducible 2026-08-20 00:35:08 +02:00
.hlint.yaml Clear the hlint backlog, including ten hints no edit could ever satisfy 2026-09-11 18:08:52 +02:00
.prettierrc New editor and AI query support (#172) 2025-05-25 07:53:20 +02:00
.rusty-hook.toml initialized FFI and now breaking down Routes into smaller modular routes to ease compile times 2024-04-30 23:49:04 +02:00
AGENTS.md Use GitHub runners and prefer local CI signoff 2026-09-08 12:24:10 +02:00
auto-instrument-config.toml Rename onboarding handlers for consistency and cleanup config 2025-11-17 09:25:29 +01:00
cabal.project Back off background job polling when worker slots are full (#539) 2026-09-07 22:51:07 +02:00
cabal.project.freeze hasql-interpolate + record-dot migration: derived ENUM/CITEXT decoders (#409) 2026-06-02 22:45:05 +02:00
CONTRIBUTING.md ci: reuse an already-built image, and document running CI locally (#493) 2026-08-16 20:24:40 +02:00
DESIGN.md Default dashboard to dark mode until users choose a theme 2026-09-08 12:59:29 +02:00
docker-compose.override.yml.example docs(docker): expand override example with persistent storage and MinIO options (#391) 2026-05-23 14:34:18 +02:00
docker-compose.yml Add ANSI-colored summary column rendering for CLI logs search (#340) 2026-03-15 02:48:58 +01:00
Dockerfile Dockerfile: filter list-bin output to the binary path line 2026-09-08 23:04:12 +02:00
Dockerfile.deps fix(docker): copy shared/ and cli/ cabal files into the deps image 2026-08-10 18:28:24 +02:00
fourmolu.yaml make fmt. and improve github actions to compile rust and copy .so files 2025-07-07 01:08:49 +02:00
hie.yaml Cherry pick files (#232) 2025-12-18 12:13:39 +01:00
LICENSE Update LICENSE 2025-11-25 16:01:12 +01:00
Makefile Build the timefusion image from a ref, not the working tree 2026-09-10 10:42:25 +02:00
monoscope.cabal Merge master: keep the issue page's new section split under the new names 2026-09-11 15:56:03 +02:00
package-lock.json fix(dashboards): stabilize grid hydration 2026-08-14 13:20:55 +02:00
package.json fix(dashboards): stabilize grid hydration 2026-08-14 13:20:55 +02:00
package.yaml Show users the schema Monoscope has been learning for them 2026-09-10 15:53:24 +02:00
playwright.config.js fix(dashboards): stabilize grid hydration 2026-08-14 13:20:55 +02:00
PRODUCT.md feat(design): commit imppecable design's assets 2026-07-13 18:38:07 -07:00
QUALITY-SWEEP-NOTES.md docs(sweep): the questions blob had the same read-modify-write shape 2026-09-04 11:56:00 +02:00
README.md fix: align severity schema and examples with stored fields (#517) 2026-09-07 03:39:04 +02:00
Setup.hs build everything in multistage docker images. 2025-09-14 19:12:41 +02:00
weeder.toml chore(weeder): root the server closure, delete the one real dead binding 2026-09-04 05:53:12 +02:00

Monoscope Logo

Open-source observability platform with S3 storage

Ingest and explore logs, traces, and metrics stored in your S3 buckets. Query with natural language. Create AI agents that detect anomalies and send daily/weekly reports to your inbox.

GitHub Release License Haskell Discord

Website • Playground • Discord • Twitter • Documentation


Monoscope Dashboard

What is Monoscope?

Monoscope is an open-source observability platform that stores your telemetry data in S3-compatible storage. Self-host it or use our cloud offering.

Core capabilities:

  • 💰 S3 storage — Store years of logs, metrics, and traces affordably in your own S3 buckets
  • 💬 Natural language queries — Search your data using plain English via LLMs
  • 🤖 AI agents — Create agents that run on a schedule to detect anomalies and surface insights
  • 📧 Email reports — Receive daily/weekly summaries of important events and anomalies
  • 🔭 OpenTelemetry native — 750+ integrations out of the box
  • ⚡ Live tail — Stream logs and traces in real-time
  • 🕵️ Unified view — Correlate logs, metrics, traces, and session replays in one place

Cloud vs Self-hosted

In both options, you bring your own S3 buckets—your data stays yours.

Cloud Self-hosted
Storage Your S3 buckets Your S3 buckets
Compute Managed by us You manage
Auth & SSO Built-in DIY
Alert channels Slack, PagerDuty, etc. Basic email
Pricing Usage-based Free (AGPL-3.0)

→ Start free on Cloud or continue below to self-host.


Quick Start

git clone https://github.com/monoscope-tech/monoscope.git
cd monoscope
docker-compose up

Visit http://localhost:8080 (default: admin/changeme)

Send Test Data

Populate your dashboard with test telemetry:

monoscope auth login

# Single event — see your message appear in the dashboard
monoscope send-event -m "Hello from Monoscope"

# Sustained load — stress-test the pipeline
monoscope telemetrygen --kind=trace --rate=5 --count=50

CLI

Manage your Monoscope project from the terminal — search logs, query metrics, manage monitors and dashboards, triage issues, and more.

curl https://monoscope.tech/install.sh | sh
monoscope auth login

See the CLI reference for the full command list.

Agentic pipeline

Every CLI command emits a stable JSON envelope, so you can chain discovery → search → triage without manual munging. This is the same pipeline a Claude Code skill runs end-to-end:

# 1. What services exist? (Precomputed; no aggregation query needed.)
SVC=$(monoscope facets resource.service.name --top 1 \
        | jq -r '.["resource.service.name"][0].value')

# 2. Grab one error event from that service — id only, ready to chain.
ID=$(monoscope logs search 'severity.severity_text=="error"' \
        --service "$SVC" --first --id-only)

# 3. Pull the surrounding 5 minutes of traffic, with a per-trace summary
#    showing which other services were affected.
monoscope events context --window 5m --summary \
  --at "$(monoscope events get "$ID" | jq -r .timestamp)" \
  | jq '.traces | sort_by(-.error_count) | .[0:3]'

# 4. Acknowledge the open issue once you have a hypothesis.
monoscope issues list --service "$SVC" --status open \
  | jq -r '.data[].id' | head -3 \
  | xargs -I {} monoscope issues ack {}

Each step's output shape is documented and stable:

Command Envelope
facets [FIELD] {<field_path>: [{value, count}, ...]}
events search (and logs/traces) {events: [...], count, has_more, cursor}
events context --summary {events, count, traces: [{trace_id, services, span_count, error_count}]}
issues list, monitors list, ... {data: [...], pagination: {has_more, total, cursor, page, per_page}}
auth status (agent mode) {authenticated, method, api_url, project}

Set MONOSCOPE_AGENT_MODE=1 (or run with --agent) to force JSON output and disable interactive prompts — auto-detected when CI or CLAUDE_CODE is set.

Claude Code Skills

Let Claude investigate incidents, triage alerts, and write KQL queries using the monoscope CLI — install the skills plugin:

# Claude Code
claude plugin marketplace add monoscope-tech/skills
claude plugin install monoscope-skills@monoscope-skills

# or via npx (Cursor, Cline, Copilot, and other agents)
npx skills add monoscope-tech/skills

Restart Claude Code after installation. Skills activate automatically when relevant — e.g. "investigate the 500 errors in payment-api" or "do an on-call sweep".

See github.com/monoscope-tech/skills for the full skill list and documentation.


MCP Server

Monoscope exposes itself as a Model Context Protocol server at /api/v1/mcp, so any MCP-aware client (Claude Desktop, Cursor, Cline, custom agents) can search events, manage monitors and dashboards, triage issues, and run composite workflows like search_events_nl (natural-language → KQL) and analyze_issue (LLM-assisted root-cause).

{
  "mcpServers": {
    "monoscope": {
      "url": "https://api.monoscope.tech/api/v1/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Every public REST endpoint is auto-registered as a verb-first tool (list_monitors, search_events, mute_monitor, …). See the MCP reference for the full protocol, tool catalog, and examples.


Integration

Auto-instrument your apps

Python
pip install opentelemetry-distro opentelemetry-exporter-otlp
opentelemetry-bootstrap -a install
OTEL_SERVICE_NAME="my-app" \
OTEL_EXPORTER_OTLP_ENDPOINT="http://localhost:4317" \
opentelemetry-instrument python myapp.py
Node.js
npm install --save @opentelemetry/auto-instrumentations-node
OTEL_SERVICE_NAME="my-app" \
OTEL_EXPORTER_OTLP_ENDPOINT="http://localhost:4317" \
node --require @opentelemetry/auto-instrumentations-node/register app.js
Java
curl -L https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/latest/download/opentelemetry-javaagent.jar -o otel-agent.jar
OTEL_SERVICE_NAME="my-app" \
OTEL_EXPORTER_OTLP_ENDPOINT="http://localhost:4317" \
java -javaagent:otel-agent.jar -jar myapp.jar
Kubernetes
# Install OpenTelemetry Operator
kubectl apply -f https://github.com/open-telemetry/opentelemetry-operator/releases/latest/download/opentelemetry-operator.yaml

# Configure auto-instrumentation
kubectl apply -f - <<EOF
apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
  name: my-instrumentation
spec:
  exporter:
    endpoint: http://monoscope:4317
  propagators:
    - tracecontext
    - baggage
EOF

# Annotate your deployments for auto-instrumentation
kubectl patch deployment my-app -p \
  '{"spec":{"template":{"metadata":{"annotations":{"instrumentation.opentelemetry.io/inject-java":"my-instrumentation"}}}}}'

Natural Language Queries

Query your telemetry data in plain English:

  • "Show me all errors in the payment service in the last hour"
  • "What caused the spike in response time yesterday?"
  • "Which endpoints have the highest p99 latency?"

AI Agents & Reports

Create AI agents that monitor your systems on a schedule:

  • Scheduled analysis — Agents run at intervals you define (hourly, daily, weekly)
  • Anomaly detection — Automatically surface unusual patterns in logs, metrics, and traces
  • Email reports — Receive summaries of important events and insights directly in your inbox
  • Customizable focus — Configure agents to watch specific services, error types, or metrics

Architecture

graph LR
    A[Your Apps] -->|Logs/Metrics/Traces| B[Ingestion API]
    B --> C[TimeFusion Engine]
    C --> D[(S3 Storage)]
    D --> E[Query Engine]
    E --> F[Dashboards]
    D --> G[AI Agent Scheduler]
    G -->|LLM Analysis| H[Anomaly Detection]
    H --> I[Email Reports]
    H --> J[Alert Channels]

Project Structure

Monoscope is organized into four primary components:

  • app/ — Haskell server binary (WAI/Yesod web application)
  • cli/ — Command-line interface for managing projects, querying data, and automating workflows
  • web-components/ — Custom UI elements (Web Components) for dashboards and log exploration
  • src/ — Core Haskell library exporting shared types, utilities, and business logic

Powered by TimeFusion

Monoscope is built on TimeFusion, our open-source time-series database for observability workloads.

🗄️ S3-native Data lives in your S3 buckets—no vendor lock-in
🐘 PostgreSQL compatible Use any Postgres client or driver
⚡ 500K+ events/sec Columnar storage with Apache Arrow
💵 Pay only for S3 No expensive proprietary storage fees

How It Compares

Feature Monoscope Datadog Elastic Prometheus
S3/Object Storage ✅ Native ❌ ✅ ✅
Natural Language Query ✅ ❌ ❌ ❌
AI Agents & Reports ✅ Built-in ❌ Add-on ❌ ❌
Open Source ✅ AGPL-3.0 ❌ ✅ ✅
Self-hostable ✅ ❌ ✅ ✅

Screenshots

Log Explorer - Unified View

Logs and trace spans displayed together in context for complete observability.

Log Explorer Main View

Trace Context Integration

See detailed trace information alongside logs for debugging complex distributed systems.

Log Explorer with Trace Context

Dashboard Analytics

Real-time metrics and performance monitoring with AI-powered insights.

Dashboard Analytics View

Trusted by Leading Companies

Andela Partna GrovePay SameDay
Platnova PayFonte ThePeer BlockRadar

"Monoscope notifies us about any slight change on the system. Features that would cost us a lot more elsewhere." — Samuel Joseph, Woodcore


Documentation


Roadmap

  • Custom dashboards builder
  • More out-of-the-box dashboards
  • AIOps workflow builder
  • Full migration to TimeFusion storage engine
  • Metrics aggregation rules
  • Multi-tenant workspace support
  • More alert channel integrations

See our public roadmap for details and to vote on features.


Community

💬 Discord • 🐛 Issues • 🐦 Twitter


License

AGPL-3.0. See LICENSE for details.

For commercial licensing options, contact us at hello@monoscope.tech.


Star on GitHub