No default alarm severity for datasources
Bug #1771015 reported by
Ifat Afek
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Vitrage |
Invalid
|
Low
|
Unassigned | ||
Bug Description
When a new datasource is created, or a new resource type is added through the static datasource, there is a need to create a status mapping file under /etc/vitrage/
There is a code that determines that if such a file doesn't exist, then default.yaml is used.
This code doesn't seem to work lately, need to check why.
Revision history for this message
| Ifat Afek (ifat-afek) wrote | #1 |
| Changed in vitrage: | |
| status: | New → Invalid |
To post a comment you must log in.
Doesn't reproduce.