filter resource file request

[ignite-404]

drop those

[gregkalapos]

You don't want the agent to capture those, right?

Some options we can do here:

• Add a config to disable capturing those (e.g. based on extension)
• Not capturing those et all (probably not the way to go)
• Do something on the UI/APM Server

I'm also asking on other channels what other agents do.

[gregkalapos]

Here is what the Java agent does: https://www.elastic.co/guide/en/apm/agent/java/current/config-http.html#config-ignore-urls

[SergeyKleyman]

@hiwjcn Could you add a little bit more about your use case? I have a feeling that you might be using ElasticApmModule from Elastic.Apm.AspNetFullFramework - is it correct? If so please take a look at #346 - by adding managedHandler to modules precondition monitoring can be limited to dynamic pages (URLs handled by ASP.NET) excluding static content.

[ignite-404]

@SergeyKleyman hey bro,im using asp.net core

Elastic.Apm.All, Version=1.0.0.0, Culture=neutral, PublicKeyToken=ae7400d2c189cf22

app.UseElasticApm(config);

and configuration like this:

  "ElasticApm": {
    "LogLevel": "Debug",
    "ServerUrls": "http://3h.elk.hiwj.cn:8200",
    "TransactionSampleRate": 1.0
  }

[ignite-404]

@SergeyKleyman @gregkalapos is there any api like this:

app.UseElasticApm(config,option=>
{
option.filter.add(url=>!url.endwith(".css"));
option.filter.add(url=>!url.endwith(".js"));
option.filter.add(url=>regex.match(url));
});

[gregkalapos]

@SergeyKleyman @gregkalapos is there any api like this:

app.UseElasticApm(config,option=>
{
option.filter.add(url=>!url.endwith(".css"));
option.filter.add(url=>!url.endwith(".js"));
option.filter.add(url=>regex.match(url));
});

No, we don't have it in .NET. We know other agent have similar filters. We already had some initial discussion about this, no final decision if we add it to .NET or not - probably it'd make sense to add it.

[gregkalapos]

Also related: https://discuss.elastic.co/t/how-to-exclude-signalr-requests-from-collected-transactions/203848

[gregkalapos]

Some update on this:
In #792 we introduced a filter API - with that you'll be able to filter out specific requests. This feature will be out with the next release.