Rename "auto" to "javaagent" in modules

[trask]

Another part of #1186

This includes #1186 (comment):

Trying out shortening the name opentelemetry-javaagent-instrumentation-api --> opentelemetry-javaagent-api

But not the shortened package rename yet, because still thinking about #1186 (comment).

[anuraaga]

SGTM

[iNikem]

LGTM but one question: why we have to repeat JAVAagent? Maybe just agent?

[trask]

LGTM but one question: why we have to repeat JAVAagent? Maybe just agent?

I like changing it here:

• armeria-1.0
  • javaagent -> agent
  • library
  • testing

since library in this context doesn't really correspond to package name / artifact name either.

For other places, I'm torn:

io.opentelemetry.agent

• opentelemetry-agent-cats
• opentelemetry-agent-api
• opentelemetry-agent
• opentelemetry-agent-spi
• opentelemetry-agent-exporters-otlp
• opentelemetry-agent-exporters-jaeger
• opentelemetry-agent-exporters-zipkin
• opentelemetry-agent-exporters-logging
• Internal components of the agent (maybe we don't need to publish?)
  • opentelemetry-agent-internal-bootstrap
  • opentelemetry-agent-internal-tooling

I like the shorter agent, but also we were trying to avoid confusion with external agents, e.g. OpenTelemetry collector agent.

[iNikem]

Does anybody call Otel Collector an "agent"?

[trask]

Does anybody call Otel Collector an "agent"?

Yeah, https://opentelemetry.io/docs/collector/about/

Also, when most ops people hear "agent", they think of out-of-process agent (like the collector agent), as opposed to in-process agent (like a javaagent). Some discussion about this occurred here: https://github.com/open-telemetry/oteps/blob/master/text/0001-telemetry-without-manual-instrumentation.md

[iNikem]

Let it be "javaagent" then