app-insights-php / client Goto Github PK

Hello, we recently had the problem that there was a large amount of requests that blocked our ports.
The timeout was probably 30 seconds, and we opened more requests to Azure Server than available ports.

Is it possible that a large number of requests were not considered and thus there may be problems in the event of a server failure if the requests are not accepted by the Azure Server?

Can this still be adjusted so that only a maximum number of requests are opened simultaneously to avoid overloading the local server?
Thank you!

Currently there is no limit on how large telemetry client queue can grow. If used in some long running backend processes it can even cause memory overflow that could break the process.

I think we should look for a way to tell client to do auto flush when queue size is greater than 5mb (this value should be configurable).

To reduce resource consumption we can try to calculate each new entry size and then just increase the current size pointer in the client.

Since microsoft/application-insights is abandoned, is there any plans on not relying on that SDK?

The app-insights-php/client package seems to be using an older version of psr/log preventing it to be used along with Laravel 10, are there any plans to use psr/log ^2.0 || ^3.0 instead ?

Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- laravel/framework[v10.0.0, ..., v10.2.0] require monolog/monolog ^3.0 -> satisfiable by monolog/monolog[3.0.0, ..., 3.3.1].
- monolog/monolog[3.0.0, ..., 3.3.1] require psr/log ^2.0 || ^3.0 -> satisfiable by psr/log[2.0.0, 3.0.0].
- You can only install one version of a package, so only one of these can be installed: psr/log[1.0.0, ..., 1.1.4, 2.0.0, 3.0.0].
- app-insights-php/client 0.2.11 requires psr/log ^1.1 -> satisfiable by psr/log[1.1.0, ..., 1.1.4].
- app-insights-php/app-insights-php-bundle 0.2.10 requires app-insights-php/client ^0.2.11 -> satisfiable by app-insights-php/client[0.2.11].
- Root composer.json requires app-insights-php/app-insights-php-bundle ^0.2.10 -> satisfiable by app-insights-php/app-insights-php-bundle[0.2.10].
- Root composer.json requires laravel/framework ^10.0 -> satisfiable by laravel/framework[v10.0.0, ..., v10.2.0].

Before stable release documentation for the client should be created and linked from the https://github.com/app-insights-php/app-insights-php-bundle documentation.

We should mention there that using trackMetric is not recommended by Microsoft and if needed its better to use trackEvent

Currently in case of App Insights server error Client will try to put all logs into the cache (if failure cache configured).
When that happens several times in a row next flush might also fail because of too many items in the queue.
Solution for that problem would be to catch this particular exception, try to divide queue into 2 pieces and repeat that recursively until success.