Get Started
| Product | Versions |
|---|---|
| .NET |
README
MyCSharp.HttpUserAgentParser
Fast HTTP User-Agent parsing for .NET.
Repository: https://github.com/mycsharp/HttpUserAgentParser
Install
dotnet add package MyCSharp.HttpUserAgentParser
Quick start (no DI)
string userAgent = "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36";
HttpUserAgentInformation info = HttpUserAgentParser.Parse(userAgent);
// or: HttpUserAgentInformation.Parse(userAgent)
Dependency injection
If you want to inject a parser (e.g., in ASP.NET Core), use IHttpUserAgentParserProvider.
No cache
services
.AddHttpUserAgentParser();
ConcurrentDictionary cache
services
.AddHttpUserAgentCachedParser();
// or: .AddHttpUserAgentParser<HttpUserAgentParserCachedProvider>();
Telemetry (EventCounters)
Telemetry is:
- Opt-in: disabled by default (keeps hot path overhead-free)
- Low overhead: counters are only written when a listener is attached
Enable telemetry (Fluent API)
services
.AddHttpUserAgentParser()
.WithTelemetry();
EventSource + counters
EventSource: MyCSharp.HttpUserAgentParser (constant: HttpUserAgentParserEventSource.EventSourceName)
parse.requests(incrementing)parse.duration(ms, event counter)cache.hit(incrementing)cache.miss(incrementing)cache.size(polling)
Monitor with dotnet-counters
dotnet-counters monitor --process-id <pid> MyCSharp.HttpUserAgentParser
Telemetry (native Meters)
In addition to EventCounters, this package can emit native System.Diagnostics.Metrics instruments.
Telemetry is:
- Opt-in: disabled by default (keeps hot path overhead-free)
- Low overhead: measurements are only recorded when enabled
Enable meters (Fluent API)
services
.AddHttpUserAgentParser()
.WithMeterTelemetry();
Meter + instruments
Meter: MyCSharp.HttpUserAgentParser (constant: HttpUserAgentParserMeters.MeterName)
parse.requests(counter)parse.duration(histogram, ms)cache.hit(counter)cache.miss(counter)cache.size(observable gauge)
Export to OpenTelemetry
You can collect these EventCounters via OpenTelemetry metrics and export them (OTLP, Prometheus, Azure Monitor, …).
Packages you typically need:
OpenTelemetryOpenTelemetry.Exporter.OpenTelemetryProtocol(or another exporter)OpenTelemetry.Instrumentation.EventCounters
Example (minimal):
using OpenTelemetry.Metrics;
using MyCSharp.HttpUserAgentParser.Telemetry;
builder.Services.AddOpenTelemetry()
.WithMetrics(metrics =>
{
metrics
.AddEventCountersInstrumentation(options =>
{
options.AddEventSources(HttpUserAgentParserEventSource.EventSourceName);
})
.AddOtlpExporter();
});
If you also use the MemoryCache/AspNetCore packages, add their EventSource names too.
Export native meters to OpenTelemetry
If you enabled native meters (see above), collect them via AddMeter(...):
using OpenTelemetry.Metrics;
using MyCSharp.HttpUserAgentParser.Telemetry;
builder.Services.AddOpenTelemetry()
.WithMetrics(metrics =>
{
metrics
.AddMeter(HttpUserAgentParserMeters.MeterName)
.AddOtlpExporter();
});
Export to Application Insights
There are two common approaches:
1) Recommended: OpenTelemetry → Application Insights
Collect with OpenTelemetry (see above) and export to Azure Monitor / Application Insights using an Azure Monitor exporter. This keeps your pipeline consistent and avoids custom listeners.
Typical packages (names may differ by version):
OpenTelemetryOpenTelemetry.Instrumentation.EventCountersAzure.Monitor.OpenTelemetry.Exporter
2) Custom EventListener → TelemetryClient
If you prefer a direct listener, you can attach an EventListener and forward values as custom metrics.
High-level idea:
- Enable the EventSource
- Parse the
EventCounterspayload - Track as Application Insights metrics
Notes:
- This is best-effort telemetry (caches can race)
- Keep aggregation intervals reasonable (e.g. 10s)
Downloads by Version
Similar & Alternative Packages
Hand-picked matching NuGet libraries based on tags & ecosystem
Depended On By
Find packages that declare this package as a dependency. NuGet does not provide a reverse-dependency endpoint, so candidates are checked on demand.
Adoption Assessment
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.