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.

Sign up for GitHub

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

Jump to bottom

Allow disabling default elasticsearch output for parser job #8

Closed
hannayurkevich opened this issue Nov 17, 2016 · 1 comment
Closed

Allow disabling default elasticsearch output for parser job #8

hannayurkevich opened this issue Nov 17, 2016 · 1 comment
Assignees
@hannayurkevich
Labels
deployment done enhancement parsing

Comments

@hannayurkevich
Copy link
Collaborator

For those cases where you want to specify all your own outputs via logstash_parser.outputs.

This issue was moved from logsearch/logsearch-boshrelease#191 original issue.
@hannayurkevich hannayurkevich self-assigned this Nov 17, 2016
@hannayurkevich hannayurkevich mentioned this issue Nov 24, 2016
Merged
hannayurkevich added a commit to hannayurkevich/logsearch-boshrelease that referenced this issue Nov 28, 2016
@hannayurkevich
Allow disabling default elasticsearch output for parser job
5e1fbea 
Fix for cloudfoundry-community#8.
Property 'logstash_parser.outputs' is set with list of logstash output plugins, by default it is set to 'elasticsearch' plugin.
Rename 'logstash_parser' elasticsearch properties to follow the same naming convention - 'logstash_parser.elasticsearch.*'.
Add logstash-templates tests to test input_and_output.conf.erb template with different configurations.
Minor reqork in test scripts - all tests are run with default rake task.
Use FileUtils.* methods in Rakefile 'cleanup' tasks.
hannayurkevich added a commit to hannayurkevich/logsearch-boshrelease that referenced this issue Nov 28, 2016
@hannayurkevich
Allow disabling default elasticsearch output for parser job
0b3fcf0 
Fix for cloudfoundry-community#8.
Property 'logstash_parser.outputs' is set with list of logstash output plugins, by default it is set to 'elasticsearch' plugin.
Rename 'logstash_parser' elasticsearch properties to follow the same naming convention - 'logstash_parser.elasticsearch.*'.
Add logstash-templates tests to test input_and_output.conf.erb template with different configurations.
Minor reqork in test scripts - all tests are run with default rake task,
remove target folder from git.
Use FileUtils.* methods in Rakefile 'cleanup' tasks.
hannayurkevich added a commit to hannayurkevich/logsearch-boshrelease that referenced this issue Nov 28, 2016
@hannayurkevich
Allow disabling default elasticsearch output for parser job
be2d582 
Fix for cloudfoundry-community#8.
Property 'logstash_parser.outputs' is set with list of logstash output plugins, by default it is set to 'elasticsearch' plugin.
Rename 'logstash_parser' elasticsearch properties to follow the same naming convention - 'logstash_parser.elasticsearch.*'.
Add logstash-templates tests to test input_and_output.conf.erb template with different configurations.
Minor reqork in test scripts - all tests are run with default rake task,
remove target folder from git.
Use FileUtils.* methods in Rakefile 'cleanup' tasks.
hannayurkevich added a commit to hannayurkevich/logsearch-boshrelease that referenced this issue Nov 28, 2016
@hannayurkevich
Allow disabling default elasticsearch output for parser job
d89fced 
Fix for cloudfoundry-community#8.
Property 'logstash_parser.outputs' is set with list of logstash output plugins, by default it is set to 'elasticsearch' plugin.
Rename 'logstash_parser' elasticsearch properties to follow the same naming convention - 'logstash_parser.elasticsearch.*'.
Add logstash-templates tests to test input_and_output.conf.erb template with different configurations.
Minor reqork in test scripts - all tests are run with default rake task,
remove target folder from git.
Use FileUtils.* methods in Rakefile 'cleanup' tasks.
@hannayurkevich hannayurkevich mentioned this issue Nov 28, 2016
Merged
@Infra-Red
Copy link
Member

Merged in #15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hannayurkevich hannayurkevich

Labels
deployment done enhancement parsing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Infra-Red @hannayurkevich