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

Adds FAQ to Beats doc #1051

Merged
merged 1 commit into from
Mar 2, 2016
Merged

Conversation

dedemorton
Copy link
Contributor

Changes for #699.

First pass. I decided to add common FAQ questions to the FAQ for each Beat rather than having a separate section in libbeat for an FAQ (because I just think it's easier for users).

@elastic/beats There were a few sections that I haven't completed yet (commented out in the source). I would appreciate some input on those sections if you have it to offer. I also think some of the explanations should be fleshed out (for example, where we talk about why Packetbeat is missing long running transactions, it would be good to explain what users can do to fix the problem).

=== Can I read log files from network volumes?

We do not recommend reading log files from network volumes. Whenever possible, install Filebeat on the host machine and
send the log files directly from there. Reading files from network volumes (especially on Windows) can have unexpected side
effects. For example, changed file identifiers may result in Filebeat reading a log file from scratch again.

// === Why isn’t Filebeat collecting lines from my file?
Copy link

Choose a reason for hiding this comment

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

  1. check if can filebeat send to logstash/elasticsearch (e.g. logstash connection established)
  2. ignore_older by default 24h. If file is older, it can not be send. (limit removed in master branch with introduction of close_older)

Copy link
Contributor

Choose a reason for hiding this comment

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

@ruflin isn't ignore_older by default set to 0 in master?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll add this for now and when the code in master is available in a release, we can remove point #2 about the default for ignore_older being 24h.

@monicasarbu
Copy link
Contributor

LGTM

@dedemorton dedemorton force-pushed the beats_issue#699 branch 2 times, most recently from 2d43933 to c74d46e Compare March 1, 2016 23:43
@urso
Copy link

urso commented Mar 2, 2016

LGTM

@monicasarbu
Copy link
Contributor

@dedemorton can you please rebase?

monicasarbu added a commit that referenced this pull request Mar 2, 2016
@monicasarbu monicasarbu merged commit 02a9a3a into elastic:master Mar 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants