In this case the call must appear before the statement. Make another request to the endpoint and view the resulting trace in . Using Visualization to Implement Automated Instrumentation this time the same query generates multiple spans to provide more granular information about the query. Any libraries in Copy Finally remove the manual span copy of the endpoint Make a request to the endpoint and view the resulting trace in Using and implementing visualizations of automated instrumentation you should see a more granular span showing the different steps as a request passes through your code. In particular you should see new spans generated by .
The library showing requests being passed th photo editing servies rough various middleware and request handlers. Note See the registry for a list of available instrument libraries. Reducing the performance impact of tracing If your application sends a large number of spans to the collector, it can have a significant impact on the performance of your application. This is usually not a problem in a development environment but can become a problem in production. There are some things you can do to alleviate this situation. Batch Send Traces Currently you are using send tracking. This is inefficient because it sends the span at once. You can make the following changes in your file to use Replication in production.
Note that you are still using it in a development environment. a big issue. This ensures that traces are displayed as soon as they are generated during development. Sending fewer spans via sampling Probability sampling is a technique that allows trace users to reduce span collection performance costs by using random sampling techniques. Using this technique you can reduce the number of spans sent to the collector while still providing a good representation of what is happening in your application. Updated to use probability sampling replication just like batch processing you only incorporate probability sampling.
發表於 2023-12-28 18:24:58
