# \[GSoC 2026\] OpenTelemetry scaling strategies

**URL:** <https://community.jenkins.io/t/gsoc-2026-opentelemetry-scaling-strategies/36647>\
**Category:** GSoC\
**Created:** [March 25, 2026, 8:20pm UTC](https://community.jenkins.io/t/gsoc-2026-opentelemetry-scaling-strategies/36647 "2026-03-25T20:20:11Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![SalmanDeveloperz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/salmandeveloperz/32/20363_2.png) [@SalmanDeveloperz](https://community.jenkins.io/u/SalmanDeveloperz)\
**Post date:** [March 26, 2026, 10:27am UTC](https://community.jenkins.io/t/gsoc-2026-opentelemetry-scaling-strategies/36647/3 "2026-03-26T10:27:51Z")

</div>

Strong architectural thinking, Pratham! The agent+ gateway pattern makes sense  
for large-scale K8s environments.

One scoping question for mentors: Given the project goal is “to help enhance  
observability of Jenkins jobs on [ci.jenkins.io](http://ci.jenkins.io)” within a 175-hour medium project,

should we prioritize:

a) Full multi-tier architecture (agent DaemonSets+ gateway+ HPA/KEDA) from day one  
b) Simpler gateway pattern first, with agent layer as future scaling enhancement

In my PoC, the gateway-only approach achieved 80%+ data reduction with tail-based sampling while keeping deployment straightforward.

Would be worth hearing from the infrastructure team on their Kubernetes setup  
and whether node-level collectors are needed from day one.

cc: @shivaylamba @krisstern

---

_[View the full topic](https://community.jenkins.io/t/gsoc-2026-opentelemetry-scaling-strategies/36647)._