Merge pull request #1047 from cloudfoundry/open-telem-tidy

Updates doc and adds packaging entry for new otel framework

Author: pivotal-david-osullivan

config/packaging.yml

@@ -151,6 +151,10 @@ new_relic_agent:
   name: New Relic Agent
   release_notes: '[Release Notes](https://docs.newrelic.com/docs/release-notes/agent-release-notes/java-release-notes/)'
 
+open_telemetry_javaagent:
+  name: Open Telemetry Agent
+  release_notes: '[Release Notes](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases)'
+
 postgresql_jdbc:
   name: PostgreSQL JDBC Driver
   release_notes: '[ChangeLog](https://jdbc.postgresql.org/documentation/changelog.html)'

docs/framework-open_telemetry_javaagent.md

@@ -26,11 +26,13 @@ and bind it to their application. The service MUST contain the string `otel-coll
 For example, to create a service named `otel-collector` that represents an environment named `cf-demo`, you could use the following commands:
 
 ```
-$ cf cups otel-collector -p '{"otel.resource.attributes": "deployment.environment=cf-demo"}'
+$ cf cups otel-collector -p '{"otel.exporter.otlp.endpoint" : "https://my-collector-endpoint", "otel.exporter.otlp.headers" : "authorization=Basic SOMEBAS64STRING","otel.exporter.otlp.protocol" : "grpc", "otel.traces.exporter" : "otlp", "otel.metrics.exporter" : "otlp", "otel.resource.attributes": "deployment.environment=cf-demo"}'
 $ cf bind-service myApp otel-collector
 $ cf restage myApp
 ```
 
+Additional configuration options for the Agent can be found [here](https://opentelemetry.io/docs/instrumentation/java/automatic/agent-config/#configuring-with-environment-variables)
+
 ### Choosing a version
 
 Most users should skip this and simply use the latest version of the agent available (the default).