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

Agent configuration tweaks #16240

Merged
merged 3 commits into from
Feb 12, 2020
Merged

Agent configuration tweaks #16240

merged 3 commits into from
Feb 12, 2020

Conversation

ph
Copy link
Contributor

@ph ph commented Feb 11, 2020

  • 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)).
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ingest (Project:fleet)

@ph ph changed the title Agent tweaks Agent configuration tweaks Feb 11, 2020
@ph ph self-assigned this Feb 11, 2020
@ph
Copy link
Contributor Author

ph commented Feb 11, 2020

fyi @michalpristas

@ph
Copy link
Contributor Author

ph commented Feb 12, 2020

@ruflin Changes made lets get this in.

- metricset: process
dataset: system.process
processes: ["firefox*"]
include_top_n:
Copy link
Contributor

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?

Copy link
Contributor Author

@ph ph Feb 12, 2020

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:

process.include_top_n:
by_cpu: 5 # include top 5 processes by CPU
by_memory: 5 # include top 5 processes by memory

Copy link
Contributor

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
Copy link
Contributor

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?

Copy link
Member

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.

Copy link
Contributor Author

@ph ph Feb 12, 2020

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 :)

Copy link
Contributor

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

Copy link
Contributor Author

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

@ph ph merged commit 662d0b4 into elastic:fleet Feb 12, 2020
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
* 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.
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