Salesforce Usage Monitoring with Nebula Logger?

[KarciSF]

I think we've found an excellent tool for logging with Nebula Logger, which comes packed with fantastic features. Thank you very much for providing it as an open-source resource.

However, I'm also exploring options for monitoring the usage of newly released features, such as flows, custom APIs (including standard APIs), or understanding how often different elements/paths are executed within flows. Let me share a few examples:

1. Path Analysis within Flows: For complex flows that have multiple branches or decision points, I'm interested in tracking which paths are most commonly taken. This data could be invaluable for optimizing the flow's design, making it more intuitive for users, and ensuring that critical features are easily accessible.

2. Feature Adoption: After rolling out new features in flows, or custom code, I want to monitor their adoption rate. This involves tracking how often these new features are used and by whom, which can provide insights into their effectiveness and user acceptance.

3. Custom API Tracking: When deploying a custom API endpoints that allows external systems to communicate with our org, it's crucial to track the frequency of these API calls

4. Standard API Consumption: I'm uncertain about the feasibility of tracking standard API usage. In some scenarios, other internal tech teams use standard APIs, and as the org owner, we would appreciate having control and an overview of their use. My idea is to eventually transition to using only custom APIs for greater control over our org, although I'm still evaluating whether this aligns with best practices. Understanding which APIs are most frequently called can aid in optimizing our Salesforce org's performance and managing API call limits.

So the whole goal is to monitor flows by tracking how frequently each specific flow is executed, identifying the main drop-off points, understanding when users exit the screen flow, determining the overall completion rate, and analyzing the number and percentage of different paths/elements accessed within the flow relative to the total number of executions. Additionally, it would be beneficial to identify the most utilized flows within the organization.

All this information can facilitate more data-driven decision-making and work prioritization.

Now, the question arises: Is Nebula Logger suitable for this purpose as well? Would it be more prudent to explore a different tool, or perhaps develop a custom object, employing a logic similar to Nebula Logger utilizing platform events to channel this data into an object specifically tailored for tracking usage?

[KarciSF]

Btw, I believe there's no need for further discussion on my part. After giving it some thought, I've concluded that creating a specialized solution might be more appropriate, given that Nebula Logger isn't primarily designed for this kind of monitoring. While it might be possible to adapt Nebula Logger for this purpose, I'm not convinced it's the most efficient approach.

If anyone has a different perspective or additional insights, I'd greatly appreciate hearing your thoughts. Otherwise, I'm inclined to mark this topic as resolved.