-
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
Enabling migration.enabled: true in metricbeat.yml breaks the writing of metricbeat index template to elasticsearch #11271
Labels
Comments
ruflin
added a commit
to ruflin/beats
that referenced
this issue
Mar 18, 2019
* rabbitmq.node.name was duplicated and alias pointed to itself * rabbitmq.connection.name was falsely migrated to `rabbitmq.name` Also adding tests to Filebeat and Metricbeat to ensure this does not happen again in the future. Closes elastic#11271
Opened #11284 with a fix and added tests to make sure this does not happen again. |
ruflin
added a commit
that referenced
this issue
Mar 18, 2019
* rabbitmq.node.name was duplicated and alias pointed to itself * rabbitmq.connection.name was falsely migrated to `rabbitmq.name` Also adding tests to Filebeat and Metricbeat to ensure this does not happen again in the future. Closes #11271
ruflin
added a commit
to ruflin/beats
that referenced
this issue
Mar 18, 2019
* rabbitmq.node.name was duplicated and alias pointed to itself * rabbitmq.connection.name was falsely migrated to `rabbitmq.name` Also adding tests to Filebeat and Metricbeat to ensure this does not happen again in the future. Closes elastic#11271 (cherry picked from commit feaef40)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If user enables migration.enabled: true in metricbeat.yml - metricbeat cannot write the indexpattern template [metricbeat-7.0.0-rc1] into elasticsearch.
This is what the ES logs say:
The text was updated successfully, but these errors were encountered: