Hi Ryan,

The handle count on its own is not a reason for concern, as SLProtocol may have a large amount of resources that it needs to manage associated with the number of elements it has.

While this may seem high, it’s not necessarily indicative of a problem in itself, especially for long-running or resource-intensive services. I checked some of our internal systems, and it is not uncommon to have SLProtocol with numbers similar to yours.

That said, it is something that can be checked by enabling trending on those metrics and verifying that there are no underlying issues, such as handle leaks or inefficient resource management.

If the handle count continues to increase, then we could be in a scenario of a leak, but if the system is not suffering from performance degradation, then it should not be a reason for concern.