- Home
- Skills
- DevOps & Cloud
- Send .NET Telemetry to Flare (OpenTelemetry)
Send .NET Telemetry to Flare (OpenTelemetry)
Wire an ASP.NET Core or worker app's logs, traces and metrics to a self-hosted Flare instance over plain OTLP, then verify the data arrived.
Free
Works with the AI Agents you already use
Send .NET Telemetry to Flare (OpenTelemetry)
Example session with this skill installed
Send this ASP.NET Core app's logs, traces and metrics to my Flare instance at http://localhost:4317.
- Read your context and instructions
- Compiled the send net telemetry
Added the 5 OpenTelemetry packages, one AddOpenTelemetry() block in Program.cs, and OTEL_EXPORTER_OTLP_ENDPOINT in launchSettings. Built clean. Started the app and hit /; logs, a trace and runtime metrics should appear in Flare (dashboard http://localhost:7777). Metrics export every 60s, so give them a minute.
Connects securely to your tools. The creator never sees your data.
About this skill
Instrument a .NET app so its logs, traces and metrics flow into Flare, a self-hosted, OpenTelemetry-native observability platform, using only the stock OpenTelemetry SDK. No agent, no proprietary format, no vendor lock-in.
What your agent will do
- Detect whether the repo uses .NET Aspire, plain ASP.NET Core, or a worker service, and pick the matching setup.
- Add the OpenTelemetry packages and a single
AddOpenTelemetry()block (ASP.NET Core,HttpClientand runtime instrumentation, plus your ownActivitySourceandMeternames). - Configure the destination through standard
OTEL_EXPORTER_OTLP_*environment variables (gRPC:4317or HTTP:4318, optional ingest key, optional trace sampling). - Add Flare next to an exporter you already have (Aspire dashboard, another backend) without tripping the SDK's
UseOtlpExportervsAddOtlpExporterconflict. - Build, run, and check the data actually shows up in Flare, with log lines linking to their traces.
- Diagnose the usual failures: wrong port for the protocol, 401 from a missing ingest key, proxy 301/308 redirects, missing logs.
Good to know
- Free. The generated code was compile-checked against OpenTelemetry .NET 1.20.1.
- Needs a reachable Flare instance. The skill includes quick-start commands (
flare startvia npm, ordocker compose up) if you don't have one yet. - Server-side .NET only; Flare has separate guides for browser, MAUI and Orleans.
Covers server-side .NET apps. Browser, MAUI and Orleans apps have their own Flare guides. Does not install or operate Flare itself beyond the quick-start commands. Packages in the generated code were compile-checked against OpenTelemetry .NET 1.20.1; check the telemetry actually appears in your Flare dashboard after wiring.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 14 days ago
- Free with an Agensi account
Requires