-
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
Fail to load index template of type index
#22482
Comments
Pinging @elastic/integrations-services (Team:Services) |
Hi there, Version: 7.10.0 |
Unfortunately, I cannot reproduce your issue. |
Elasticsearch |
What is the output of E.g. I get this: {
"template": {
"mappings": {
"_meta": {
"beat": "filebeat",
"version": "7.10.0"
},
"date_detection": false,
"dynamic_templates": [
],
"properties": {}
}
} Also, could you share your |
I don't have any custom configuration for I just tried to load using |
component
index
Elasticsearch This command works: Create a legacy tempate
This one does not work: Try to create an index template
The error I get:
|
I can reproduce it now, thanks for the help. |
## What does this PR do? This PR fixes the `setup.template.type` setting. When `index` were selected, Beats based the generated index on the legacy format, not on the component. This prevented Beats from loading the index. ## Why is it important? `setup.template.type=index` was broken. Now it is fixed. ## How to test this PR locally ``` ./filebeat setup --index-management -E setup.template.type=index ``` ## Related issues Closes #22482
) ## What does this PR do? This PR fixes the `setup.template.type` setting. When `index` were selected, Beats based the generated index on the legacy format, not on the component. This prevented Beats from loading the index. ## Why is it important? `setup.template.type=index` was broken. Now it is fixed. ## How to test this PR locally ``` ./filebeat setup --index-management -E setup.template.type=index ``` ## Related issues Closes elastic#22482 (cherry picked from commit 569268d)
) This PR fixes the `setup.template.type` setting. When `index` were selected, Beats based the generated index on the legacy format, not on the component. This prevented Beats from loading the index. `setup.template.type=index` was broken. Now it is fixed. ``` ./filebeat setup --index-management -E setup.template.type=index ``` Closes elastic#22482 (cherry picked from commit 569268d)
…22742) This PR fixes the `setup.template.type` setting. When `index` were selected, Beats based the generated index on the legacy format, not on the component. This prevented Beats from loading the index. `setup.template.type=index` was broken. Now it is fixed. ``` ./filebeat setup --index-management -E setup.template.type=index ``` Closes #22482 (cherry picked from commit 569268d)
…22741) ## What does this PR do? This PR fixes the `setup.template.type` setting. When `index` were selected, Beats based the generated index on the legacy format, not on the component. This prevented Beats from loading the index. ## Why is it important? `setup.template.type=index` was broken. Now it is fixed. ## How to test this PR locally ``` ./filebeat setup --index-management -E setup.template.type=index ``` ## Related issues Closes #22482 (cherry picked from commit 569268d)
For confirmed bugs, please report:
Run Beats setup to set up the new Filebeat index template,
e.g.
filebeat setup -e --index-management -E setup.template.type=index
The following error was printed in console:
Snippet of the index template printed in console:
mappings
andsettings
should be nested undertemplate
object.The text was updated successfully, but these errors were encountered: