-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Logs] Document the central logs source setting #4316
Comments
@flash1293 @Kerry350 I was hoping I could get some input from you on this issue and on what needs to be documented. @gbamparop mentioned that it would be a good candidate for 8.16 docs, but I don't have much background on this one so I would appreciate your help filling in the gaps here. |
@mdbirnstiehl No problem. I'll write up some bullet points tomorrow on what this affects and how 👍 |
@mdbirnstiehl From a high level what we've done is added a new advanced setting (called Log sources) which now influences how multiple Observability solutions access logs data (rather than having disjointed methods - hardcoded indices lists etc). The hope is that this brings consistency to data access and less surprises for users (https://github.com/elastic/logs-dev/issues/138). Right now these changes affect the following UIs:
The setting is now the default option associated with the logs UI settings. This also means the setting still influences the indices queried in log threshold rules unless the user has manually changed to "indices" or "data view". Those two options are now deprecated. (https://github.com/elastic/logs-dev/issues/170)
|
A new central setting as described in https://github.com/elastic/logs-dev/issues/138 should be introduced. Once in place, it can be used in progressively more places throughout the observability solution.
Project Link
The text was updated successfully, but these errors were encountered: