Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Core API needs a diagnostics interface
See original GitHub issueWe need a general diagnostics interface that can plug in to Maven, javax.annotation.processing, or a generic log output. The interface should be able to capture error, warning, info, and debug level events with full source/location context.
This API would be consumed by build steps as well as the core code.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Application Diagnostics in .NET Core 3.1 - Damian ... - YouTube
What do you do when your .NET Core application doesn't behave the way you expect? Maybe it's slower since the last deployment or...
Read more >Checking the Health of Your ASP.NET Core APIs
Health checks are part of the middleware and libraries provided by ASP.NET Core to help report the health of application infrastructure ...
Read more >Health checks in ASP.NET Core | Microsoft Learn
Diagnostics.HealthChecks , a health check library for ASP.NET Core apps, includes a health check that runs against a SQL Server database.
Read more >Diagnostics in .Net Core 3: Listening to outbound HTTP requests
A look into the EventCounters API in .Net Core 3, and seeing how we can capture outbound HTTP Requests.
Read more >Google.Cloud.Diagnostics.AspNetCore
Google.Cloud.Diagnostics.AspNetCore is an ASP.NET Core instrumentation library for Google Logging, Error Reporting and Tracing.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I suppose the real issue isn’t the lack of API, but rather that we aren’t using it in any way at present.
It’s still needed IMO - as are a few other really fundamental design changes - but OTOH we’ve scraped by with our current more ad-hoc error reporting. Perhaps as the world turns, the right conditions to fix this will come around again in the future and we can address it then.