opentelemetry-php icon indicating copy to clipboard operation
opentelemetry-php copied to clipboard

PHP integration with OpenTelemetry (OTel)

Open pizicaiman opened this issue 5 months ago • 4 comments

###Base: the project API request QPS is high

  • the api request cost more time
  • the api container always run failed

###Ask: ways to solve the question?

  • give more resource cpu could be better however how to balance resource to api or monior otel data
  • define to control the different api about monitoring range

I hope to find friends who have encountered similar issues and can provide some feasible solutions or ideas.

pizicaiman avatar Jun 11 '25 03:06 pizicaiman

Hi @pizicaiman is the problem above something related to the PHP implementation of OpenTelemetry? If so, would this issue be better under https://github.com/open-telemetry/opentelemetry-php ? Or https://github.com/open-telemetry/opentelemetry-php-contrib?

danielgblanco avatar Jun 16 '25 09:06 danielgblanco

@open-telemetry/php-approvers PTAL, let us know if you want us to move the issue over into one of your repos.

svrnm avatar Jun 18 '25 09:06 svrnm

@open-telemetry/php-approvers PTAL, let us know if you want us to move the issue over into one of your repos.

@svrnm Please can you move it across to https://github.com/open-telemetry/opentelemetry-php issue board so we can take a look? Thanks in advance.

ChrisLightfootWild avatar Jun 18 '25 11:06 ChrisLightfootWild

Hi @pizicaiman 👋

Please could you provide some further details of the way your application is currently instrumented (composer show open-telemetry/* should produce a good list as a starting point).

Can you then describe how you are exporting the telemetry - is that to a sidecar with otel-collector or directly with some remote OTLP backend?

ChrisLightfootWild avatar Jun 18 '25 13:06 ChrisLightfootWild

ping @pizicaiman - we will try to help you but need some more information from you 😺

brettmc avatar Jul 08 '25 04:07 brettmc

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Oct 18 '25 05:10 stale[bot]