aaryan-srivastava-glean opened a new issue, #35539: URL: https://github.com/apache/beam/issues/35539
### What would you like to happen? As of now, when google cloud profiler is enable for java jobs; the profiler service name is set based on the job's metadata. Quite similar to how python supports passing of a custom profiler service name (https://github.com/apache/beam/issues/26280), can we also get support to have custom profiler service names for Java? It would improve usability to dedupe across many different runs for Java jobs and combine profiler views across job versions! ### Issue Priority Priority: 2 (default / most feature requests should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [x] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@beam.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
