Chore/general client analytics #394
Conversation
🦋 Changeset detectedLatest commit: 05e1832 The changes in this PR will be included in the next version bump. This PR includes changesets to release 13 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| intermediateQuery += | ||
| queryParams.length === 0 | ||
| ? ` WHERE connected_at >= $1 AND connected_at <= $2` | ||
| : ` AND connected_at >= $${queryParams.length + 1} AND connected_at <= $${queryParams.length + 2}`; |
There was a problem hiding this comment.
This appears to add multiple WHERE clauses if both date_range and client_id/user_id is specified - will this work? Same for cursor below.
There was a problem hiding this comment.
It builds up the query based on the query parameter legth and the adds a and or where, I have added some tests to validate functionality. The query looks like this:
SELECT id, user_id, client_id, user_agent, sdk, jwt_exp::text AS jwt_exp, disconnected_at, connected_at::text AS connected_at, disconnected_at::text AS disconnected_at FROM connection_report_events WHERE client_id = $1 AND user_id = $2 AND connected_at >= $3 AND connected_at <= $4 ORDER BY connected_at DESC
Added general connection analytics query for Mongo and Postgres report storage.
Query will return a paginated list of connections which can be filtered by:
Purpose: Ability to get more granular user/client specific connection data.
Bugfix:
report update UTC time for PostgresReportStorage