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!

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...