You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2020. It is now read-only.
Gathering information on API queries and responses will be vauable for a number of reasons, including providing us as developers with information about how end users are interacting with this data, and providing information about the types and locations of services that residents are looking for that can be relayed to government and organization decision makers.
I feel like this is still ticket is still in discovery - I'm not really sure what kind of analytics we're interested in, not do I have solid thoughts on how to implement. So, let's talk about that first.
The text was updated successfully, but these errors were encountered:
OK, I do have some thougths on what data I'm interested in. What queries is the API receiving? (assuming that queries represent requests for centers/classes/events based on location/time/other attributes) What responses are we returning for queries? Are there queries that are returning 0 results?
There's also part of me that thinks implementation could be dead simple: just write some middleware or response hook that writes the request and response to a database. I'd like to see if there are already Django/Python modules for doing this, but as a last resort I suspect writing this ourselves would be pretty quick.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Gathering information on API queries and responses will be vauable for a number of reasons, including providing us as developers with information about how end users are interacting with this data, and providing information about the types and locations of services that residents are looking for that can be relayed to government and organization decision makers.
I feel like this is still ticket is still in discovery - I'm not really sure what kind of analytics we're interested in, not do I have solid thoughts on how to implement. So, let's talk about that first.
The text was updated successfully, but these errors were encountered: