Hi Naim,
The community can provide more technical or use case suggestions. In the meantime, I wanted to share some documentation we have.
Service endpoint:
A business transaction offers a view of application performance that cuts across the environment, reflecting all services that participate in fulfilling the transaction. Another way of viewing application performance, however, focuses on the performance of a particular service independently of the business transactions that use it.
Like business transactions, service endpoints give you key performance indicators, metrics, and snapshots. However, they provide that information exclusively in the context of that service, omitting business transaction context or downstream performance data.
Information Point:
You can use information points to define custom metrics based on methods you configure.
Information points are similar to data collectors. However, while data collectors show application data in the context of a business transaction, information points reflect data state across all invocations of a method, independently of business transactions. They also let you apply computations to the values, for example, representing the sum or average for a method return value or input parameter.
This topic describes how to configure and use information points. For information on data collectors, see Data Collectors.
