The Microbus framework uses environment variables for various purposes:
PROD, LAB, LOCAL, TESTING)Environment variables may also be set by placing an env.yaml file in the working directory of the executable running the microservice. The bundled example application includes such a file at main/env.yaml.
Before connecting to NATS, a microservice can’t communicate with other microservices and therefore it can’t reach the configurator microservice to fetch the values of its config properties. Connecting to NATS therefore must precede configuration which means that initializing the NATS connection itself can’t be done using the standard configuration pattern. Instead, the NATS connection is initialized using environment variables: MICROBUS_NATS, MICROBUS_NATS_USER, MICROBUS_NATS_PASSWORD and MICROBUS_NATS_TOKEN.
The MICROBUS_DEPLOYMENT environment variable determines the deployment environment of the microservice: PROD, LAB, LOCAL or TESTING. If not specified, PROD is assumed, unless connecting to nats://localhost:4222 or nats://127.0.0.1:4222 in which case LOCAL is assumed.
The plane of communication is a unique prefix set for all communications sent or received over NATS. It is used to isolate communication among a group of microservices over a NATS cluster that is shared with other microservices.
If not explicitly set via the SetPlane method of the Connector, the value is pulled from the MICROBUS_PLANE environment variable. The plane must include only alphanumeric characters and is case-sensitive.
Applications created with application.NewTesting set a random plane to eliminate the chance of collision when tests are executed in parallel in the same NATS cluster, e.g. using go test ./... -p=8.
This is an advanced feature and in most cases there is no need to customize the plane of communications.
The MICROBUS_LOCALITY environment variable sets the locality of the microservice, which is used as the basis for locality-aware routing.
Setting the MICROBUS_LOG_DEBUG environment variable to any non-empty value is required for microservices to log debug-level messages.
Microbus is using OpenTelemetry to send tracing spans to Jaeger via the OTLP HTTP collector. In order to enable tracing, the endpoint of the collector must be set in the OTEL_EXPORTER_OTLP_TRACES_ENDPOINT or OTEL_EXPORTER_OTLP_ENDPOINT environment variables.