Migrate .NET Logging to OpenTelemetry and Flare
Move a .NET app from Serilog, NLog, ZLogger or ILogger-only logging (and from another OTLP backend such as SigNoz) to Flare over OTLP, with a parallel-run cutover and no lost or duplicated logs.
Free
Works with the AI Agents you already use
Migrate .NET Logging to OpenTelemetry and Flare
Example session with this skill installed
We log with Serilog to Seq. Move us to Flare but keep Seq working until we've compared them.
- Read your context and instructions
- Compiled the migrate net logging
Kept the Seq sink and added Serilog.Sinks.OpenTelemetry (4.2.0) pointed at Flare via Flare:Endpoint, service.name = orders. No call sites changed. Built clean. Both sinks receive every event, so log counts can be compared in the two UIs over the same hour. Cutover checklist and the one line to remove the Seq sink are in the report; I did not remove it.
Connects securely to your tools. The creator never sees your data.
About this skill
Move a .NET app's logging to Flare over plain OpenTelemetry (OTLP) without rewriting call sites and without a risky big-bang cutover.
What your agent will do
- Detect what you log with today (Serilog, NLog, ZLogger, plain
ILogger) and where it goes (Seq, Elasticsearch, files, Application Insights, SigNoz or another OTLP backend). - Wire the right OTLP path for each library, using package versions Flare's docs record as run against a live stack: the native OpenTelemetry logging provider for
ILogger/ZLogger, the officialSerilog.Sinks.OpenTelemetrysink, and NLog's OTLP target. - Add Flare next to your existing sink first, so both receive every event while you compare.
- Avoid the classic traps: duplicate logs when Serilog and the OpenTelemetry provider both fire, NLog printing raw message templates, a missing
service.name, and anAuthorizationheader Flare rejects. - Plan a parallel run when moving off SigNoz or another OTLP backend (repoint, or have Flare forward a copy), then a cutover checklist.
- Recreate alerts with the
flareCLI and point you at Flare's Grafana-compatible APIs for existing dashboards.
Good to know
- Free. Serilog snippets were compile-checked.
- Old data is not copied across, and there is no one-click importer for another tool's dashboards or alerts.
- The skill never removes your old sink or changes anything outside the logging setup without asking.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Covers .NET logging libraries that Flare's docs verify (Microsoft.Extensions.Logging, ZLogger, Serilog, NLog). log4net and non-.NET stacks are out of scope. Historical data is not copied from the old backend, and there is no automatic importer for dashboards or alerts from SigNoz or other tools; the skill recreates alerts with the flare CLI and points at Flare's Grafana-compatible APIs for dashboards. Serilog snippets were compile-checked; the full flow was not run end to end against a live Flare for this skill, though Flare's docs record these packages as run against a live stack.
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 buying a skill.
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 to use
No account required to browse
Trust & safety
Security scan
Security scan passed 14 days ago
- Free with an Agensi account
- Software
- .NET app.NET CLIFlare instance
The app must log with Serilog, NLog, ZLogger or Microsoft.Extensions.Logging. Flare must be running and reachable on OTLP port 4317 (gRPC) or 4318 (HTTP).