AppD Archive

Configure Custom Exit Point for .NET Generic method

CommunityUser
Splunk Employee
Splunk Employee

This is the first time I am setting up a custom exit point.

My exit point is for a Redis cache provider.

I have a class such as:

namespace CacheProviders.Redis

{

...

public sealed partial class RedisCacheProvider : ICacheProvider

{

...

public T Get<T>(object key) {...}

public bool Set<T>(object key, T val) {...}

...

}

So, in the custom exit point defintion, I have:

"with a class name that" equals: CacheProviders.Redis.RedisCacheProvider

"method name": Get

but this doesn't seem to wotk.

Is there a special way to deal with generic methods?

Do I need to specify method name as "Get<T>"? or "Get<>"?

Also, does the class name have to be fully qualified like "CacheProviders.Redis.RedisCacheProvider, MyAssembly"?

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Jeff,

I ran this by our support team who suggested the following:

For generic classes or methods, you need to append a `N to the name where N is the number of parametrers.

 
For example, consider the class:
AppDynamics.MyClass<T>

 Class name equals AppDynamics.MyClass`1

 
For a the follwing method:
MyMethod<Type1, Type2>

 Method name equals MyMethod`2

 
0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...