Are we adding a new java service?
Wouldn't be better to allow users to enable/disable instrumentation on the services we already have?

I'm hesitant to add to the existing resource requirements given the kubecon feedback for a smaller footprint

I'm hesitant to add to the existing resource requirements given the kubecon feedback for a smaller footprint

same here

I don't anticipate this being used in a local deployment -- my 0.02 is that we should address the resource issue by creating a "minimal" set of services to be run locally while allowing for a larger set to be run in "production" deployments

The advantage of adding a net new service here is that it's a terminal/leaf service, ensuring that disabling the service or running it without instrumentation doesn't impact the rest of the deployment.

Let's create a plan to have minimal and more expansive deployment scenarios before we add anything new. Something we can discuss in detail at the next SIG meeting.

Can merge post simple+ demo

FYI I'm building this in my own repo and publishing it in the meantime - https://github.com/austinlparker/otel-demo-business-metrics

I'll be able to publicly share the demo flow for this in a few weeks

This PR was marked stale due to lack of activity. It will be closed in 7 days.

After we get #872 finished and merged, we can look to move this as an additional service in an optional module/preset.

This PR was marked stale due to lack of activity. It will be closed in 7 days.

This PR was marked stale due to lack of activity. It will be closed in 7 days.

This PR was marked stale due to lack of activity. It will be closed in 7 days.

This PR was marked stale due to lack of activity. It will be closed in 7 days.

Closed as inactive. Feel free to reopen if this PR is still being worked on.