-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Agent configuration tweaks #16240
Agent configuration tweaks #16240
Conversation
ph
commented
Feb 11, 2020
•
edited
Loading
edited
- Added period for the system/metrics
- Remove a few slashes for dataset.
- Move queue_url to the input level followed @kaiyan-sheng's advice.
- double-check credentials support for AWS
- Added period for the system/metrics - Remove a few slashes for dataset. - Move queue_url to the input level followed @kaiyan-sheng's [advice](elastic#15940 (comment)).
Pinging @elastic/ingest (Project:fleet) |
fyi @michalpristas |
@ruflin Changes made lets get this in. |
- metricset: process | ||
dataset: system.process | ||
processes: ["firefox*"] | ||
include_top_n: |
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.
is this something we understand or is it input/processor config?
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.
This is something we relay to the input module section in metricbeat. This required a bit of massaging:
beats/metricbeat/modules.d/system.yml
Lines 19 to 22 in 69cd8d8
process.include_top_n: | |
by_cpu: 5 # include top 5 processes by CPU | |
by_memory: 5 # include top 5 processes by memory | |
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.
in this case it's fine
- id?: {id} | ||
metricset: s3access | ||
dataset: aws/s3access | ||
dataset: aws.s3access |
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.
will we provide some mapping logic between dataset-metricset in case metricset is missing?
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.
This could become tricky as we would need a lookup. It is not always straight forward.
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.
So in this case explicit >= magic :)
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.
so we should always have metricset stated in case of metricbeat input
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.
Yes, we would say that metricset is indeed mandatory, without that we cannot pick up the right module when launching metricbeat and we configure the module with a custom option like {metricset}.include_top_n
* Agent tweaks - Added period for the system/metrics - Remove a few slashes for dataset. - Move queue_url to the input level followed @kaiyan-sheng's [advice](elastic#15940 (comment)). * few issues with aws * Define queue on stream.