Show notification in the fuel-web UI if stats collecting is broken
Bug #1454337 reported by
Alexander Kislitsky
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Won't Fix
|
High
|
Fuel Python (Deprecated) | ||
Bug Description
In case of deleting or disabling keystone stats collecting user we should show notification in the Fuel web UI.
Notification should be shown only once, only for operational clusters if
customer is opted-in to the sending stats.
If, for example, user was disabled. We should show notification on the first failed stats collecting. After that user can be enabled and again disabled. In this case we should again show notification only once.
| Changed in fuel: | |
| importance: | Medium → High |
| Changed in fuel: | |
| assignee: | Fuel Python Team (fuel-python) → Artem Roma (aroma-x) |
| description: | updated |
| summary: |
- Show notification in the nailgun UI if stats collecting is broken + Show notification in the fuel-web UI if stats collecting is broken |
| tags: | added: feature |
| Changed in fuel: | |
| assignee: | Artem Roma (aroma-x) → Fuel Python Team (fuel-python) |
Revision history for this message
| Sheena Conant (sheena-conant) wrote | #1 |
Revision history for this message
| Alexander Kislitsky (akislitsky) wrote | #2 |
| Changed in fuel: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
I would argue that we should not be presenting any errors or information regarding the status of prod stats collection. This is a silent process intended to help us better understand how our customers are using/not using Fuel.
If we were to generate this error, what action would we expect the user to take? I think it's unreasonable to ask them to do something to remediate an issue on something that is not benefiting them directly.