Automatic configuration
We added new instrumentation in the past three chapters and watched how we could generate more information each time we instrumented the code. We will now see how we can continue to provide the same level of telemetry but simplify our lives by removing some of the code. The first code we will be removing is the configuration code we extracted into the common.py module. If you recall from previous chapters, the purpose of the configure_tracer, configure_meter, and configure_logger methods, which we will review in detail shortly, is to do the following:
- Configure the emitter of telemetry.
- Configure the destination and mechanism to output the telemetry.
- Add resource information to identify our service.
As we saw earlier in this chapter, the opentelemetry-instrument script enables us to remove the code doing the configuration by interpreting environment variables or command-line arguments that will do the same thing. We will review the configuration...
