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

Update "ELK Flow Collector" documentation to account for the FlowAggregator #2058

Closed
antoninbas opened this issue Apr 9, 2021 · 1 comment · Fixed by #2094
Closed

Update "ELK Flow Collector" documentation to account for the FlowAggregator #2058

antoninbas opened this issue Apr 9, 2021 · 1 comment · Fixed by #2094
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/documentation Categorizes issue or PR as related to a documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@antoninbas
Copy link
Contributor

@antoninbas antoninbas added kind/bug Categorizes issue or PR as related to a bug. kind/documentation Categorizes issue or PR as related to a documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Apr 9, 2021
@srikartati
Copy link
Member

Modified in PR #2094

  • The information about configuring "interval" in the logstash configuration seems outdated. The Configuration points to the FlowExporter configuration instead of the FlowAggregator configuration. It should also explain why / when changing the default value (60s) is necessary.

This interval was removed in PR #2089

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/documentation Categorizes issue or PR as related to a documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants