What is the function of defining classes/methods as custom services?

Defining classes and methods as custom services primarily serves the purpose of monitoring non-standard transactions. In many applications, especially those with complex architectures, standard monitoring tools may not capture specific interactions or workflows that are unique to the application. By implementing custom services, developers can define what constitutes a significant transaction for their business logic, allowing them to track performance, detect anomalies, and gain insights into the application's behavior related to those custom-defined operations.

This ability ensures that non-standard transactions, which might not correlate directly to typical metrics collected by default monitoring tools, are still thoroughly observed. It enhances the granularity of monitoring, helping organizations to understand both performance impacts and user experiences beyond standard use cases. Therefore, creating custom services enables teams to have visibility over tailored transaction flows crucial for their unique business requirements.