Continuing from my previous article on HTTPS Endpoint Troubleshooting in Logic App Standard, I introduce a new tool: HttpTraceForLogicApps.
The EventListener
class in C# is a powerful tool for monitoring and debugging. It allows applications to subscribe to internal events, particularly useful for tracing HTTP requests in .NET Core. By implementing custom listeners, developers can gain insights into the internal workings of their applications. For more detailed information, check out Microsoft's documentation on EventListener and this guide on using EventListener for performance monitoring.
The tool is designed to be run in the Kudu console. Here's a quick guide on how to get it up and running:
git clone https://github.com/mbarqawi/HttpTraceForLogicApps.git
Cd HttpTraceForLogicApps
dotnet publish
Cd bin\Release\net8.0\publish
HttpsTrace.exe https://wrong.host.badssl.com/ >ssl.json
the Result will be stored in a text file.
results from the captured log where the error is RemoteCertificateNameMismatch
If you like to remove the tool after using it
go to the CMD in Kudu and run the below command.
rmdir /S HttpTraceForLogicApps
HttpTraceForLogicApps, Are you sure (Y/N)? y
When working with Logic Apps, you might encounter certificate-related issues such as custom certificate (CS) errors or hostname mismatches. These issues can be tricky, but understanding their root causes is key to resolving them.
HttpTraceForLogicApps is a step forward in simplifying the debugging process for Logic Apps. By leveraging the EventListener in C#, it provides a clear view of HTTP traffic, aiding in the quick resolution of issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.