fixing quoteservice metrics exporting

[brettmc]

Changes

metrics exporting was quietly failing due to misconfiguration. Update some packages to pick up the relevant bugfix, and use OTEL_EXPORTER_OTLP_ENDPOINT so that metrics, traces and eventually logs can use it.
In passing, enable some logging which makes future errors more obvious.

Merge Requirements

For new features contributions please make sure you have completed the following
essential items:

• CHANGELOG.md updated to document new feature additions
• Appropriate documentation updates in the docs

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

Fixes: #775

[julianocosta89]

Thanks for taking care of this @brettmc!
Could you add a CHANGELOG entry?

[julianocosta89]

Tried to build it locally and started getting the following msg in the logs:

[2023-03-15T10:50:43.962596+00:00] otel-php.WARNING: tracestate discarded, invalid member:  {"source":"OpenTelemetry\\API\\Trace\\TraceState"} []

Is that expected?

[brettmc]

@julianocosta89 no it's not expected...but I did turn on some logging so it's possible that it's a problem that's always been there but not noticed. I didn't see this when just calling the service directly (which would make sense, there is no distributed tracing).

To replicate, do I just bring up everything and watch it run?

[julianocosta89]

@julianocosta89 no it's not expected...but I did turn on some logging so it's possible that it's a problem that's always been there but not noticed. I didn't see this when just calling the service directly (which would make sense, there is no distributed tracing).

To replicate, do I just bring up everything and watch it run?

You can run:

docker compose build quoteservice --no-cache

docker compose up

Once everything is running, you can get the logs from quoteservice:

docker logs quoteservice

[brettmc]

upstream bugfix: open-telemetry/opentelemetry-php#936

[brettmc]

ok, patched in a new version of one of our packages, the warning message is gone, and we have one less bug in our code. I think this is ready now.

[julianocosta89]

Awesome!