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

Report probing errors to teleport #586

Merged
merged 1 commit into from
Oct 17, 2023
Merged

Conversation

oxtoacart
Copy link
Contributor

@oxtoacart oxtoacart commented Oct 17, 2023

For getlantern/engineering#292

This will give us insight into whether real clients are encountering this, and what are the patterns (if any).

@oxtoacart
Copy link
Contributor Author

oxtoacart commented Oct 17, 2023

Okay, I deployed a preview of this for route 22488719-1f0c-4c2e-83a2-dead89b90fcd and the below query shows us getting the data I wanted. Also, the proxy in question has stayed up without crashing, so I'm going to go ahead and deploy.

SELECT
client_version,
client_platform,
probing_error,
APPROX_COUNT_DISTINCT(device_id) AS unique_devices
FROM `lantern-cloud.teleport.base_table`
WHERE
  TIMESTAMP_TRUNC(ts, DAY) >= TIMESTAMP("2023-10-16")
  AND name = 'proxied_bytes'
GROUP BY client_version, client_platform, probing_error
ORDER BY unique_devices DESC
LIMIT 1000

@oxtoacart oxtoacart merged commit bb2cbec into main Oct 17, 2023
2 checks passed
@oxtoacart oxtoacart deleted the report_probing_to_teleport branch October 17, 2023 15:26
@orca-glo
Copy link
Contributor

Thanks, @oxtoacart 🙏 Random bonus side effect of reading this was the prompt to refresh on anonymous fields in structs. I'm going to miss learning from you 😞

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

Successfully merging this pull request may close these issues.

2 participants