-
Notifications
You must be signed in to change notification settings - Fork 7
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
added memcached #20
Merged
Merged
added memcached #20
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
# Plugin Info | ||
version: 0.0.1 | ||
title: Memcached | ||
description: Log parser for Memcached | ||
parameters: | ||
file_path: | ||
label: Memcached Logs Path | ||
description: The absolute path to the Memcached logs | ||
type: string | ||
default: "/var/log/memcached.log*" | ||
start_at: | ||
label: Start At | ||
description: Start reading file from 'beginning' or 'end' | ||
type: enum | ||
valid_values: | ||
- beginning | ||
- end | ||
default: end | ||
|
||
# Set Defaults | ||
{{$file_path := default "/var/log/memcached.log*" .file_path}} | ||
{{$start_at := default "end" .start_at}} | ||
|
||
# Pipeline Template | ||
pipeline: | ||
- id: memcached_input | ||
type: file_input | ||
include: | ||
- {{ $file_path }} | ||
start_at: {{ $start_at }} | ||
labels: | ||
log_type: memcached | ||
output: {{.output}} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should plugins that have a single file input be log_path to match format of other plugins that have multiple log paths? They use something like general_log_path for example?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These parameter names were pulled directly from the log bundles when I generated them. I know Zack put a lot of effort into standardizing the names across bundles, so I'm guessing there's probably a good reason we did file_path over log_path. My guess is that file_path was used when there is typically one file to point at, whereas log_path was used when you can't point at a directory or glob pattern.