Best fit
Use Logister for ASP.NET Core services and C# background work.
The .NET SDK helps instrument web requests, workers, custom metrics, transactions, and scheduled check-ins. The event detail view is shaped for .NET payloads so stack, request, route, status, and runtime context stay readable.
Useful context
Connect exceptions to routes, releases, and scheduled jobs.
- Request method, URL/path, route, status, and headers can make the failing ASP.NET Core request obvious.
- Release and environment names help teams separate deploy regressions from old issues.
- Transaction metrics and check-ins help connect exceptions to performance and scheduled work health.
- Assignment filters keep project triage grounded in who owns each grouped issue.
Evaluate
Verify one exception and one operational signal.
- Create a Logister project and configure the .NET SDK with its API key.
- Trigger one controlled ASP.NET Core exception with route, method, environment, and release metadata.
- Send one check-in or transaction from the same service or worker.
- Confirm the error appears in the inbox and the operational signal appears on its product surface.
- Assign the grouped issue and confirm the project team can filter by owner.
Next steps
Install the .NET SDK and send one exception plus one check-in.
Use the .NET integration guide to wire the app, then verify grouped errors, performance, and monitor pages in Logister.