Ship with write-only creds to an S3 bucket for profile data

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

We have:

  1. A built-in profiler: https://docs.gitlab.com/ee/development/profiling.html#profiling-a-url
  2. A project that runs these and uploads the results to S3: https://gitlab.com/gitlab-com/gitlab-profiler
  3. The profile results at https://redash.gitlab.com/dashboard/gitlab-profiler-statistics

There's a gap here: it's still fairly fiddly to actually upload an HTML profile somewhere. We could fill that gap by shipping GitLab with some creds to write to an S3 bucket (or object storage of your choice) that any customer could use to send us a profile of a request.

If that's not an option, then we could at least let administrators set that value, and do so on GitLab.com, so it's easy for people with Rails console access to upload their profile results rather than try to print them as text (which is very noisy).

/cc @stanhu

Edited Sep 28, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading