Flare.Net

Languages: English  |  简体中文  |  Русский  |  Français

A self-hosted, OpenTelemetry-native observability platform for .NET — logs, traces, and metrics as first-class citizens, correlated in one place, with threshold/query-based alert rules that notify webhook/Slack, Telegram, or email on breach.

Think Seq or Datadog — but fully open source (MIT), self-hosted, and OTLP straight in with no proprietary agent or SDK to install.

OpenTelemetry first

Your application → OTLP → Flare. That's the whole ingestion story — no proprietary wire format, no agent daemon. If you're already instrumented with OpenTelemetry, Flare can consume it directly.

What Flare provides

Logs	Search, filtering, live tail, structured properties
Traces	Distributed tracing with log/trace correlation
Metrics	Explore OpenTelemetry metrics alongside logs and traces
Alerts	Threshold/query-based rules with webhook, Slack, Telegram, and email
Ingestion	OTLP receiver and pipeline health
Indexing	ClickHouse index and query/storage diagnostics
Auth	Local accounts, Entra ID, Active Directory/LDAP, OIDC, and reverse-proxy trusted headers
Views	Saved searches and reusable views

Why Flare?

• OpenTelemetry-native — no proprietary ingestion protocol; send standard OTLP telemetry directly.
• Self-hosted — your telemetry stays in your infrastructure.
• Built for .NET — first-class .NET/Aspire integration without requiring a separate agent ecosystem.
• One place for telemetry — logs, traces, and metrics are correlated rather than treated as separate products.
• Simple deployment — run it through Aspire, Docker Compose, or the Flare CLI.

Getting started

What differs is how you run Flare itself. Pick one:

• Already using .NET Aspire?

  // AppHost
  var flare = builder.AddFlare("flare");
  builder.AddProject<Projects.MyApi>("myapi").WithReference(flare).WaitForFlare(flare);

  dotnet add package Flare.Hosting.Aspire — Flare joins your AppHost as a resource, so it starts, stops, and gets discovered by your other resources the same way everything else in your graph does. Details: docs/how-to/run-with-aspire.md.

• Not using Aspire, want it running standalone?

  docker compose up

  at the repo root, with working defaults for every port and credential (copy .env.example to .env to change any). Details: docs/how-to/run-standalone.md.

• Just evaluating — no repo cloned, no .NET SDK?

  curl -fsSL https://raw.githubusercontent.com/aminparsa18/Flare.Net/main/scripts/install.sh | bash

  Installs Docker if it's missing, then pulls and starts the same standalone stack from the published images. Details: docs/how-to/run-standalone.md#zero-prerequisite-quick-install.

• Want one standing instance shared across several unrelated local projects?

  dotnet tool install --global Flare.Cli
  flare start

  A global CLI that manages the same Docker stack from anywhere, no repo checkout required. Details: docs/how-to/run-with-cli.md.

Whichever path you pick, the dashboard comes up at http://localhost:7777. Authentication is off by default — the Logs page is open the moment it's up. Turn sign-in on (local accounts, Microsoft Entra ID, Active Directory, OpenID Connect, or reverse-proxy trusted headers) from the /auth page whenever you're ready; see docs/how-to/configure-authentication.md.

Then point a logger at it — copy-paste OTLP snippets for Serilog, NLog, ZLogger, and Microsoft.Extensions.Logging live in docs/how-to/run-standalone.md (or docs/how-to/run-with-aspire.md on Aspire). For anything else — Python, Node.js, Java, Go, Kubernetes, DevOps pipelines, a log shipper, or Prometheus scrape — the dashboard's own Data sources page (nav dropdown, or the Logs page's empty state) has the same kind of copy-paste snippets; see the architecture tour for a preview.

Outgrowing a single ClickHouse node? There's an opt-in multi-node cluster setup — see docs/how-to/run-cluster-mode.md.

Local development

Standalone Docker isn't the dev-inner-loop story — see Flare.AppHost (.NET Aspire) for that, and each project's own README (e.g. src/dashboard/README.md) for running it individually.

Status

Flare is actively developed and currently provides:

• Logs
• Traces
• Metrics
• Alerts
• OTLP ingestion
• Pipeline health
• Indexing diagnostics
• Saved searches
• Authentication
• Aspire integration
• Docker deployment
• Flare CLI

Next

See docs-internal/planning/roadmap.md for what's currently open — retention/cold storage to S3-compatible object storage chief among it.

Full architecture: docs/explanation/architecture.md. Design decisions: docs-internal/adr/.

Contributing

See CONTRIBUTING.md.

License

MIT