Tunnel support for plain dotnet core console app
See original GitHub issueProblem Statement
I am looking for tunnel support compatible with the Sentry
nuget package, so I can tell my netcoreapp3.1
to use a tunnel on the local network to send Sentry logging. This is required as the machine where the console app is running on, doesn’t have access to the internet, only to the machine where the tunnel is running on.
Solution Brainstorm
Implement https://docs.sentry.io/platforms/javascript/troubleshooting/#using-the-tunnel-option for the dotnet core SDK 😃
Issue Analytics
- State:
- Created a month ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Port Tunneling for ASP.NET Core Projects - YouTube
NET Core applications and services. Community Links: https://www.theurlist.com/aspnet-standup-2022-08-26 Featuring: Carolina Uribe-Gosselin ...
Read more >Dev tunnels in Visual Studio 2022 - ASP.NET Core
The dev tunnels feature of Visual Studio 2022 enables ad-hoc connections between machines that can't directly connect to each other. A URL is ......
Read more >Create a .NET console application using Visual Studio
Create the app · Select .NET 7 (Standard-term support). · Select Do not use top-level statements. · Select Create.
Read more >ASP.NET Core
A tunnel is an HTTP endpoint that acts as a proxy between Sentry and your application. Because you control this server, there is...
Read more >Configure Twilio Webhooks with Visual Studio dev tunnels ...
In this blog post, you will learn how to retrieve the tunnel URL from your ASP.NET Core application and use it to automatically...
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 FreeTop 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
Top GitHub Comments
Thanks for reaching out! We’ll see what we can do. 😃
While that might work, it doesn’t really make sense to me to be honest. We have this nice, well documented tunnel option, which should be trivial to add to the implementation of the package here (or at least, that would be my expectation), but instead I would need to create a proxy with an additional implementation to replace the DSN with the actual one. And this would be specifically for this DSN, while the others that are already going through my tunnel (which are JS based applications) work fine without it?