Skip to content

Distinguish development, test, and prod environment for services #491

@annieke

Description

@annieke

Is your feature request related to a problem? Please describe.
Our services (at least batch-submitter and data-transport-layer) are currently environment agnostic. However, being environment-aware helps us conditionally launch monitoring apps (eg Sentry and prom-client) and send tags to them accordingly.

Describe the solution you'd like
Details need to be spiked out, but ideally during application start we can retrieve some variable for which environment the services runs in. We should also be able to tag logs with this environment.

Describe alternatives you've considered
If adding overall environment management is too much of an overhead, we could temporarily use env vars for these services such as ENABLE_SENTRY=true

Additional context
Currently only related to TypeScript services, but could be extended to other code we run.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions