-
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
Metricbeat sql module: error mapping the query property #15736
Labels
Comments
narph
added
Team:Integrations
Label for the Integrations team
Metricbeat
Metricbeat
v7.6.0
labels
Jan 22, 2020
jsoriano
added a commit
to jsoriano/beats
that referenced
this issue
Jan 22, 2020
Mapping was defined at the metricset level, but it should be defined at the module level. Add system test to earlier check documented fields. Fixes elastic#15736
jsoriano
added a commit
that referenced
this issue
Jan 22, 2020
Mapping was defined at the metricset level, but it should be defined at the module level. Add system test to earlier detect this kind of issues. Also add validation so driver and sql_query options cannot be empty. Fetch was reusing some maps when building the event, what was causing mixed data in events and panics on queries with lots of rows. Fixes #15736
jsoriano
added a commit
to jsoriano/beats
that referenced
this issue
Jan 22, 2020
Mapping was defined at the metricset level, but it should be defined at the module level. Add system test to earlier detect this kind of issues. Also add validation so driver and sql_query options cannot be empty. Fetch was reusing some maps when building the event, what was causing mixed data in events and panics on queries with lots of rows. Fixes elastic#15736 (cherry picked from commit badb2cb)
jsoriano
added a commit
to jsoriano/beats
that referenced
this issue
Jan 22, 2020
Mapping was defined at the metricset level, but it should be defined at the module level. Add system test to earlier detect this kind of issues. Also add validation so driver and sql_query options cannot be empty. Fetch was reusing some maps when building the event, what was causing mixed data in events and panics on queries with lots of rows. Fixes elastic#15736 (cherry picked from commit badb2cb)
jsoriano
added a commit
that referenced
this issue
Jan 22, 2020
Mapping was defined at the metricset level, but it should be defined at the module level. Add system test to earlier detect this kind of issues. Also add validation so driver and sql_query options cannot be empty. Fetch was reusing some maps when building the event, what was causing mixed data in events and panics on queries with lots of rows. Fixes #15736 (cherry picked from commit badb2cb)
jsoriano
added a commit
that referenced
this issue
Jan 23, 2020
Mapping was defined at the metricset level, but it should be defined at the module level. Add system test to earlier detect this kind of issues. Also add validation so driver and sql_query options cannot be empty. Fetch was reusing some maps when building the event, what was causing mixed data in events and panics on queries with lots of rows. Fixes #15736 (cherry picked from commit badb2cb)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Initial ticket #13257
An example of event to be sent to es or other output looks like:
but in the fields.yml definition
query
is not a string property:ES is returning the errors:
The text was updated successfully, but these errors were encountered: