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

Install full configs in packages #1682

Merged
merged 1 commit into from
May 23, 2016
Merged

Conversation

tsg
Copy link
Contributor

@tsg tsg commented May 20, 2016

This adds the "full" version of the configuration files to the
config path of all the artifacts.

This adds the "full" version of the configuration files to the
config path of all the artifacts.
@tsg tsg added the review label May 20, 2016
# Windows
sed -i 's|#\{0,1\}\(to_files:\).*|\1 true|' $(PREFIX)/$(BEATNAME)-win.yml
sed -i 's|#\{0,1\}\(level:\).*|\1 info|' $(PREFIX)/$(BEATNAME)-win.yml
sed -i '/log files/{n;s|#\{0,1\}path:.*|path: C:/ProgramData/winlogbeat/Logs|}' $(PREFIX)/$(BEATNAME)-win.yml
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@andrewkroh I removed these as the current defaults should work fine and I want to minimize the number of seds we do on the config files.

Copy link
Member

Choose a reason for hiding this comment

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

The only thing I will miss here is having the info level logging out of the box. When you are new first time user it's nice to have some positive feedback in the logs that its running and indexing events.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, I thought so, but that makes it inconsistent with the rest of the Beats. The reason we keep it to ERR is that WARN is too verbose in Packetbeat, maybe in other beats as well. Maybe we should move most of those WARNs to DEBUG and then switch to INFO by default.

I think our logging system, in general, is due for refactoring.

Copy link
Contributor

Choose a reason for hiding this comment

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

I did in the past quite a few changes to filebeat and libbeat to make "INFO" feasible. +1 on switching to Info and do some refactoring of packetbeat. That would be also a win that the log file gets generated by default as there are always info messages on startup.

@tsg
Copy link
Contributor Author

tsg commented May 20, 2016

jenkins, package it

@@ -33,15 +33,15 @@ cp $BEATNAME.template-es2x.json $PREFIX/$BEATNAME.template-es2x.json

# linux
cp $BEATNAME.yml $PREFIX/$BEATNAME-linux.yml
Copy link
Contributor

Choose a reason for hiding this comment

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

For linux we do not copy full?

@ruflin
Copy link
Contributor

ruflin commented May 20, 2016

LGTM

@tsg tsg mentioned this pull request May 20, 2016
14 tasks
@ruflin
Copy link
Contributor

ruflin commented May 23, 2016

@tsg @andrewkroh Merging this one as I assume we agree on improving the logging. I would even suggest to enabled info by default in a small PR and then tackle packetbeat?

@ruflin ruflin merged commit 6f04c8f into elastic:master May 23, 2016
@tsg tsg deleted the install_full_configs branch August 25, 2016 10:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants