Generate actual saturation query in manifest, not in Tamland
The following discussion from gitlab-com/runbooks!6198 (closed) should be addressed:
-
@reprazent started a discussion: (+2 comments) Perhaps we should already build the entire service-component on this side, that way we could build all the queries on this side off the fence, and what tamland queries and renders is based on that configuration.
I think that would make sense, because the other values in this
saturation.json
file are also pretty tied to our setup: other installations will not have the same services, shards, teams and whatnot.What do you think?