Determine instrumentation strategy for saved opportunities and saved searches

[mxk0]

Summary

In order to report on the Search/Opp Listing v2 enhanced deliverable, we need reliable stats on the following:

• At least 500 saved opportunities are created by at least 50 unique users
• At least 250 searches are saved by at least 25 unique users

This ticket is to explore an document how we will do this reporting.

We can see how many e.g. opportunities are saved at any given time based on what's in the saved opps db table, but for the 500 metric we should be able to count opportunities that were saved and then unsaved.

Acceptance criteria

• Discovery done, any decisions needed are made, any follow-up tickets are created

[doug-s-nava]

maybe partially a question of how "unsaves" will be implemented. If "unsaves" will be deleted from the DB then we'll have to think about this, but if there will be a column to track saved state instead, then we can just run a normal count

[mxk0]

We can get this from API logs in CloudWatch.