Apologies if this has been asked before -- what's best practices to separate environments? For inst...
b
Apologies if this has been asked before -- what's best practices to separate environments? For instance, I may have 2 products (Prod1, Prod2). Each has 2 environments (Dev, Prod). (these two products may be completely and wholly separate) Things may be named similar between environments (i..e Prod1-webapp) is the name for the webapp pods in dev and prod In addition, at least right now, if they all have a postgres database, the service graph seems to think it's all the same database. What's the best way to manage this?
b
🤦‍♂️ There's even a doc for it. Thank you! Sorry I missed the doc
v
No worries, Brad. We are working on adding
deployment.environment
as default in every doc
b
Is there also a good way to separate by product?
v
No Brad, it's in our long term roadmap. Currently you can see environments on services/traces page to differentiate environments
b
Thanks! I'll maybe just try out "prod1-dev" "prod2-prod" as 'environemnts'