CODAP-1090: Research CloudFront logs for codap.concord.org URL usage#2339
Closed
dougmartin wants to merge 2 commits intomainfrom
Closed
CODAP-1090: Research CloudFront logs for codap.concord.org URL usage#2339dougmartin wants to merge 2 commits intomainfrom
dougmartin wants to merge 2 commits intomainfrom
Conversation
Analyze AWS CloudFront access logs to understand how users launch CODAP v2 via different URL paths, informing decisions about release infrastructure. Key findings (Feb 2025 - Jan 2026): - /app is dominant: 3.3M requests (5x more than /releases/latest) - /releases/latest: 711K requests, steady usage - /releases/stable: 162K requests, collapsed in June 2025 - Clear school year pattern in /app traffic Added specs: - specs/CODAP-1090-research-cloudfront-logs/requirements.md - specs/CODAP-1090-research-cloudfront-logs/implementation.md Analysis method: AWS Athena queries against S3 logs (~9.5 GB, ~$0.05/query) Interactive results: https://codap3.concord.org/#shared=https%3A%2F%2Fcfm-shared.concord.org%2FNlLpguqSRh1GOcTkNryt%2Ffile.json
kswenson
approved these changes
Feb 5, 2026
Member
kswenson
left a comment
kswenson
left a comment
There was a problem hiding this comment.
👍 LGTM, other than the point we made at the meeting that it would be good to know more about the /releases (other) group, given that there were almost as many of those as /releases/latest.
…raffic Break out the "/releases (other)" aggregate category into individual release paths (e.g., /releases/latest, /releases/stable, /releases/build_0742). Tighten the launch-point WHERE filter to exclude intermediate directory paths and non-HTML assets, matching only index.html, the CODAP cert directory pattern, and bare redirect paths.
Member
Author
|
I added a commit with updated queries to expand the "other" group and tighten the counts so assets are ignored. Closing as this was just for research. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Analyze AWS CloudFront access logs to understand how users launch CODAP v2 via different URL paths, informing decisions about release infrastructure.
Key findings (Feb 2025 - Jan 2026):
Added specs:
Analysis method: AWS Athena queries against S3 logs (~9.5 GB, ~$0.05/query)
Interactive results: https://codap3.concord.org/#shared=https%3A%2F%2Fcfm-shared.concord.org%2FNlLpguqSRh1GOcTkNryt%2Ffile.json