[docs] Describe some basic logs filtering scenarios for out of box logging in Fuel
Bug #1449513 reported by
Bogdan Dobrelya
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Won't Fix
|
Medium
|
Fuel Documentation Team | ||
| 6.0.x |
Won't Fix
|
Medium
|
Fuel Documentation Team | ||
Bug Description
Root cause analysys is a common task for dev, QA, service teams and for cloud operators as well.
By default, Fuel provides a logs storage for many logs sources from Openstack nodes and from local services, such as mcollective or nailgun or asute, as well. We should describe some basic tricks for searching and sorting by some patterns in our ops guide.
Here is the source I suggest to use for this task https:/
| Changed in fuel: | |
| milestone: | none → 6.1 |
| importance: | Undecided → Medium |
| assignee: | nobody → Fuel Documentation Team (fuel-docs) |
| Changed in fuel: | |
| status: | New → Confirmed |
| milestone: | 6.1 → 7.0 |
| Changed in fuel: | |
| milestone: | 7.0 → 8.0 |
| tags: | added: area-docs |
Revision history for this message
| Alexey Stupnikov (astupnikov) wrote | #1 |
| Changed in fuel: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
We no longer support MOS5.1, MOS6.0, MOS6.1
We deliver only Critical/Security fixes to MOS7.0, MOS8.0.
We deliver only High/Critical/