Agent does not work on new Asp.Net Core 3.1 Project
See original GitHub issueDescribe the bug Agent does not work on new Asp.Net Core 3.1 Project. Browser loads the page forever.
To Reproduce Steps to reproduce the behavior:
- Create a new Asp.Net Core 3.1 MVC Project
- Run and see the homepage
- Stop debugging
- Add nuget package : Install-Package Elastic.Apm.AspNetCore -Version 1.5.1
- Add configuration to the appsettings.json file :
"ElasticApm": {
"SecretToken": "",
"ServerUrls": "http://localhost:8200", //Set custom APM Server URL (default: http://localhost:8200)
"ServiceName": "TestApp" //allowed characters: a-z, A-Z, 0-9, -, _, and space. Default is the entry assembly of the application
}
- Add directive to the startup.cs file:
public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
app.UseElasticApm(Configuration);
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler("/Home/Error");
// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
app.UseHsts();
}
- Press run (debug) button
Expected behavior Page to be loaded.
But browser tries to load the page forever. No exception. No content.
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (9 by maintainers)
Top Results From Across the Web
.Net Core 3.1 not yet supported in Azure Pipelines hosted ...
No, Azure Pipelines hosted agents supports .Net Core 3.1 , but the latest .net core 3.1.100 is not currently installed by default in...
Read more >Unable to get my pipeline to build a .NET core 3.1 solution
Hello,. I was able to resolve both issues using the windows-2019 hosted agent by doing the following: 1. Added the "Use .NET Core...
Read more >Upgrade of .NET agent for Azure Pipelines
We are upgrading the .NET used by Azure Pipelines agent from current .NET Core 3.1 to .NET 6. This is to support new...
Read more >Breaking changes in .NET Core 3.1
If you're migrating to version 3.1 of .NET Core or ASP.NET Core, the breaking changes listed in this article may affect your app....
Read more >Common issues related to .NET Core Applications monitoring
If the .NET Core Application that needs to be monitored does not work through IIS, you could check the handler mappings in IIS...
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
@gregkalapos interesting, now it seems to be working. So it’s Metrics related.
I’ve already updated to 1.6.0, but the issue remains. I completely understand that ‘keeps loading’ isn’t very useful, but I’m not sure where to look tbh. I’ve only tested this with an existing application, I will try again later today with a new one.
In the meantime, here is some of the extra info you requested. Hope it helps.
appsettings.json:
Diagnostic Tools, after pressing Break All:
Breaks on:
Details Caller/Callee:
Details Call Tree:
Details Modules:
Details Functions:
Let me know if you need more.