Skip to content

[Observability] Add log data sources page #1791

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

Merged
merged 18 commits into from
Jul 31, 2025

Conversation

mdbirnstiehl
Copy link
Contributor

This PR closes Issue 231.

Copy link

github-actions bot commented Jun 18, 2025

🔍 Preview links for changed docs:

🔔 The preview site may take up to 3 minutes to finish building. These links will become live once it completes.

Comment on lines 24 to 26
1. From **Stack Management** → **Saved Objects**, [export](/explore-analyze/find-and-organize/saved-objects.md) the log data views, which are stored as an `infrastructure-monitoring-log-view` saved object type, to use as a template.
1. Modify the relevant data view fields in the exported JSON.
1. Import the saved object using the [import saved objects API]({{kib-apis}}/operation/operation-importsavedobjectsdefault).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@weltenwort I pulled these instructions from a comment you made on an older issue from last year. I was hoping you could take a look and make sure this is still applicable or if there are changes that need to be made?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @mdbirnstiehl, thanks for the ping. This approach makes sense for existing deployments that don't use advanced setting mentioned above for historic reasons. Any newer deployments default to using the advanced setting and a manipulation of the log view saved object might therefore not have any effect. AFAIK in serverless that saved object type doesn't exist at all.
So if we want to include this approach I feel we should add lots of caveat warnings around it. Does that help?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @weltenwort, that does make sense. There's a discussion in the issue for this PR, where I think what we actually want to document is using the Advanced Settings saved object. I'm not sure if the process to use Advanced Settings saved object would be similar to this or if the process would differ.

Copy link
Member

@weltenwort weltenwort Jul 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The process would be similar, but the downside is that one couldn't just export/import this one setting selectively. It would always apply to all settings.

For users that use configuration management for Kibana deployments, there is the option to define overrides to individual settings in the yaml file like this:

uiSettings:
  overrides:
    'observability:logSources': ["logs-somewhere-else"]

But I'm not sure if that is an officially supported setting or not 🤔

Copy link

github-actions bot commented Jul 30, 2025

🔍 Preview links for changed docs

@mdbirnstiehl mdbirnstiehl marked this pull request as ready for review July 30, 2025 20:13
@mdbirnstiehl mdbirnstiehl requested review from a team as code owners July 30, 2025 20:13
@mdbirnstiehl mdbirnstiehl requested a review from gbamparop July 30, 2025 20:15
Copy link
Contributor

@florent-leborgne florent-leborgne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Content LGTM

@gbamparop
Copy link
Contributor

Thanks for working on this!

@mdbirnstiehl mdbirnstiehl merged commit e9c3c0c into elastic:main Jul 31, 2025
8 checks passed
@mdbirnstiehl mdbirnstiehl deleted the log-data-sources branch July 31, 2025 14:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants