-
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
Netflow filebeat 7.4.2 and template definition #14617
Comments
Steps to reproduce:
The entries with source_id and id: Eg in template: Logs |
The netflow module is not exposing the I have opened a PR to add the missing options to the netflow module in #14628. |
The exposes all of the netflow input configuration options through the netflow/log fileset. Fixes elastic#14617 Filebeat's module code was changed to allow for manifests to declare variables without default values. This means that module manifests can be written without duplicating the default values of the input types that they wrap (e.g. don't duplicate the default socket timeout value). It also changes the template evaluation to be more strict in that referencing a variable that does not exist will now cause an error instead of evaluating to "<no value>". The zeek/dhcp module referred to a variable that was not declared in its manifest. This was fixed.
Maybe I'm doing something wrong but it doesn't works related to #14618 the cache value entry is missing ? And how it works now ? in memory ?
|
Maybe this can be useful In docker:
filebeat.reference.yml
Netflow is disable ?? There is nothing in syslog except monitoring But with:
It works but template seems inactive, hundred of lines with : No template ID XXX |
As far I can tell my problem is: The netflow module is not exposing the custom_definitions and the filebeat.reference.yml is not used (at least by netflow) EDIT: Same result with filebeat modules enable netflow and values in netflow.yml |
The exposes all of the netflow input configuration options through the netflow/log fileset. Fixes elastic#14617 Filebeat's module code was changed to allow for manifests to declare variables without default values. This means that module manifests can be written without duplicating the default values of the input types that they wrap (e.g. don't duplicate the default socket timeout value). It also changes the template evaluation to be more strict in that referencing a variable that does not exist will now cause an error instead of evaluating to "<no value>". The zeek/dhcp module referred to a variable that was not declared in its manifest. This was fixed. (cherry picked from commit e08c6ec)
@andrewkroh hello, are you sure that it works with 7.5.0 ? Eg: No template ID 263 Worst if I try a wrong value, false path for custom_definitions or netflow.log.var.read_buffer=fred there is no error/warning from filebeat ? |
My improvement was backported after 7.5 was made so it will show up in 7.6.0. You could workaround this by using the netflow input directly rather than via the module. |
) The exposes all of the netflow input configuration options through the netflow/log fileset. Fixes #14617 Filebeat's module code was changed to allow for manifests to declare variables without default values. This means that module manifests can be written without duplicating the default values of the input types that they wrap (e.g. don't duplicate the default socket timeout value). It also changes the template evaluation to be more strict in that referencing a variable that does not exist will now cause an error instead of evaluating to "<no value>". The zeek/dhcp module referred to a variable that was not declared in its manifest. This was fixed. (cherry picked from commit e08c6ec)
Hello,
Option -M netflow.log.custom_definitions=file.template seems inactive
With debug mode if have many "No template for ID XXX"
Eg: No template ID 263
Packet from: xxxx.xxxx.xxx.xxx:2536 src:169765857
source_id: 169765857 is in my template file
The same file works well with logstash
Another issue without debug, packets with no template are just silently dropped
The text was updated successfully, but these errors were encountered: