BZ: 1383903. Notes and changes for for logging stack upgrade #3211
Conversation
|
@ahardin-rh - Please review. |
vikram-redhat
changed the title
| @@ -1370,6 +1370,26 @@ of Fluentd pods, the deployer does delete the *logging-fluentd* Daemonset and re | |||
| it from the *logging-fluentd-template* template. | |||
| ==== | |||
|
|
|||
| The latest EFK stack now uses Elasticsearch 2.3 with a common data model. This | |||
| means Fluentd sends logs to Elasticsearch with a new indexing pattern for | |||
| projects. The pattern is: | |||
There was a problem hiding this comment.
I think we should call out that the pattern for 'operations' logs will stay the same.
There was a problem hiding this comment.
Added a note for the operations logs.
| [IMPORTANT] | ||
| ==== | ||
| Downgrading from Elasticsearch 2.3 to Elasticsearch 1.x is not possible due to | ||
| migration to the new data model. |
There was a problem hiding this comment.
Technically this is independent of the common data model; this is simply a limitation of Elasticsearch 1.x not being able to interpret the data structure of ES 2.x.
It may not be necessary to capture that in the documentation, however it should be noted.
There was a problem hiding this comment.
I've modified this from "data model" to "data structure" to avoid confusion.
|
LGTM |
|
@danmacpherson @vikram-redhat I merged some logging content today because I did not know this work was being done: Hopefully, a simple rebase resolves this. If not, we can always revert the changes I introduced. Just a heads-up. As we approach 3.4, I am trying to knock out some dev-submitted PRs so I recommend using the "assign yourself" function to prevent team members from bumping into eachother. Thanks! |
|
@ahardin-rh - thanks. A simple rebase should solve this. |
|
@ewolinetz @danmacpherson Does this PR need to take #3081 (comment) into consideration? |
|
@adellape yes, it should have this line[1] added to it, similar to step 4 in the manual upgrades for EFK. |
danmacpherson
force-pushed
the
BZ1383903-LoggingStack
branch
2 times, most recently
from
481315e to
e3b7ad2
Compare
Adding suggestions from ewolinetz Adding suggestions from ewolinetz Updating install documentation and adding information on how to allow cluster-reader to view operations logs Follow-up to ewolinet's notes on 'rolebinding-reader'
danmacpherson
force-pushed
the
BZ1383903-LoggingStack
branch
from
fc08fa7 to
1dc4dcb
Compare
|
Squashed the commits to accommodate our publishing system |
|
Since peer and tech review has passed, I am merging this. |
Also includes PR #3172
@vikram-redhat -- Ready to review and merge