Skip to content
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

[Docs] [Filebeat] [Kibana module] Add what configuration is needed for it to work #26894

Closed
a03nikki opened this issue Jul 14, 2021 · 2 comments
Labels
docs Filebeat Filebeat Stalled Team:Elastic-Agent Label for the Agent team

Comments

@a03nikki
Copy link

a03nikki commented Jul 14, 2021

Describe the enhancement:

It would be nice if the documentation for Filebeat's kibana module included which log formats are supported and possibly how to configure it so the module worked.

Describe a specific use case for the enhancement or feature:

The Kibana module (Filebeat v7.13) does not indicate what the log format needs to be in order to work properly. By comparison, the Elasticsearch module (Filebeat v7.13) indicates use the json log format for new Elasticsearch versions.

For Kibana, it only says the default text for var.paths of

var.paths
An array of glob-based paths that specify where to look for the log files. All patterns supported by Go Glob are also supported here. For example, you can use wildcards to fetch all files from a predefined level of subdirectories: /path/to/log/*/*.log. This fetches all .log files from the subfolders of /path/to/log. It does not fetch log files from the /path/to/log folder itself. If this setting is left empty, Filebeat will choose log paths based on your operating system.

The Logging settings in Kibana page (v7.13) indicates a number of log formats are possible now.

  • logging.appenders.{NAME}.type: console or file
  • logging.appenders.{NAME}.laytout.type: pattern default, pattern custom, or json

When I was trying to quickly set this up for myself, I tried both the default pattern and json to a log file and both produced filebeat-7.13.3-* documents with the error object populated. I tried to check the source for the module, but didn't find the answer quickly there either. As it was just my lab environment, I skipped this set-up and moved onto other tasks instead of spending time to figure it out.

Related: #24136

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jul 14, 2021
@ChrsMark ChrsMark added the Team:Elastic-Agent Label for the Agent team label Jul 26, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/agent (Team:Agent)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jul 26, 2021
@botelastic
Copy link

botelastic bot commented Jul 26, 2022

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Jul 26, 2022
@botelastic botelastic bot closed this as completed Jan 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Filebeat Filebeat Stalled Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

No branches or pull requests

3 participants