Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add detection and listener counts in json api #705

Open
skanderm opened this issue Nov 5, 2024 · 4 comments
Open

Add detection and listener counts in json api #705

skanderm opened this issue Nov 5, 2024 · 4 comments

Comments

@skanderm
Copy link
Contributor

skanderm commented Nov 5, 2024

Is your feature request related to a problem? Please describe.
Orcanode monitor would like detections and listener counts displayed for each feed

Describe the solution you'd like
Once #704 is implemented, we can share the last live listener count recorded and the recent detection count.

@dthaler
Copy link
Contributor

dthaler commented Nov 6, 2024

In terms of what would be ideal (unsure whether implementable)...
Accept a parameter that indicates when the client wants the # of listeners since (e.g., 1 week, 1 month).
Then include the # of "play" (or whatever it's called) events logged, and the # of detections logged, since that time.

@skanderm
Copy link
Contributor Author

skanderm commented Nov 6, 2024

In terms of what would be ideal (unsure whether implementable)... Accept a parameter that indicates when the client wants the # of listeners since (e.g., 1 week, 1 month). Then include the # of "play" (or whatever it's called) events logged, and the # of detections logged, since that time.

That mostly sounds good to me, though we're only logging play clicks in Google Analytics. Do we want to try tracking those on the server too? Personally, I think we should just get those from GA.

@dthaler
Copy link
Contributor

dthaler commented Nov 6, 2024

In terms of what would be ideal (unsure whether implementable)... Accept a parameter that indicates when the client wants the # of listeners since (e.g., 1 week, 1 month). Then include the # of "play" (or whatever it's called) events logged, and the # of detections logged, since that time.

That mostly sounds good to me, though we're only logging play clicks in Google Analytics. Do we want to try tracking those on the server too? Personally, I think we should just get those from GA.

Does GA expose an API for querying such stats?

@skanderm
Copy link
Contributor Author

Might be worth asking @adrmac about where the data comes from for those charts he shares every week

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: triage
Development

No branches or pull requests

2 participants