You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Tracking]: Beam 3.0.0 - Milestone 1 Key Features #36173
Do we have any estimate timeline for Opentelemetry support? I do see a few related PR being merged recently. But I am not sure when Opentelemetry support will be ready.
This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.
Activity
damccorm commentedon Sep 23, 2025
Issues/PRs that stand out to me for First class ML:
Model Serving
Feature Generation
Embedding Generation
Anomaly Detection
@claudevdm @jrmccluskey @shunping @tvalentyn could you please add anything that I am missing?
jrmccluskey commentedon Sep 23, 2025
Tracking issue for Java Remote Inference filed at #36253
Would we also want to add the model evaluation work here?
damccorm commentedon Sep 23, 2025
Yes, that's a good idea
liferoad commentedon Sep 25, 2025
ML-aware API rate limiter on the SDK side could be another work. cc @tarun-google
vampire-hunter-lincoln commentedon Dec 15, 2025
Hi Beam Team,
Do we have any estimate timeline for Opentelemetry support? I do see a few related PR being merged recently. But I am not sure when Opentelemetry support will be ready.
github-actions commentedon May 15, 2026
This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.
github-actions commentedon Jun 15, 2026
This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.