No aggregator service running when the toolchain is deployed without controller
Bug #1574609 reported by
Simon Pasquier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StackLight |
Confirmed
|
Medium
|
guillaume thouvenin |
Bug Description
In a so-called dedicated StackLight environment (where you deploy only the StackLight backends), there's no aggregator service because there's no controller. As a consequence, there's no GSE metric for the StackLight backends.
tags: | added: dedicated-env |
Changed in lma-toolchain: | |
status: | In Progress → Confirmed |
Changed in lma-toolchain: | |
milestone: | none → 0.10.1 |
milestone: | 0.10.1 → 1.0.0 |
Changed in lma-toolchain: | |
milestone: | 1.0.0 → none |
To post a comment you must log in.
I proposed to fix this issue in two steps.
1) We quickly fix it without deploying the aggregator client. So this dedicated environment won't be monitored. It answers to the use case in which we want to deploy only backends and those backends will be used by other environments.
2) It is a better solution to also monitor the monitoring environment so in this step we will deploy the aggregator server. We will do this in a second step because it requires more work and currently the deployment in dedicated env is broken. So that's why I propose to fix it and then improve it.