如何避免超过1024个字段的APM场爆炸？
我们正在使用Azure App Service中运行的Nodejs的ELK APM。我们目前有APM版本1.7.16。 APM索引模式具有1467个字段，这使得在所有字段中搜索此错误：
"type" : "query_shard_exception",
"reason" : "failed to create query: field expansion matches too many fields, limit: 1024, got: 1443",
这使得很难将APM用于自由文本搜索。如果我在确切的字段名称上搜索精确的匹配，但这不如自由文本搜索有用。
我们使用nodejs库Elastic-apm节点版本 ^3.20.0。
我知道indices.query.bool.max_clause_count设置，显然可以将其设置为更高的数字。但是我不知道如何在托管弹性的托管实例上做到这一点。如果我首先可以限制APM数据中的字段数量，那就更好了。它似乎爆炸了。
有人知道我如何修复它，以便从发现窗格或APM窗格的自由文本搜索再次开始工作吗？
We are using ELK APM from NodeJS running in Azure App Service. We currently have APM version 1.7.16. The APM index patterns has 1467 fields, which makes search across all fields fail with this error:
"type" : "query_shard_exception",
"reason" : "failed to create query: field expansion matches too many fields, limit: 1024, got: 1443",
This makes it very hard to use APM for free-text searching. If I search for exact matches on exact field names it works but this is less useful than free-text search.
We use NodeJS library elastic-apm-node version ^3.20.0.
I am aware of the indices.query.bool.max_clause_count setting which apparently can be set to a higher number. But I can't figure out how to do that on hosted ELK instances on elastic. It would be better if I could limit the amount of fields in the APM data in the first place. It seems to have exploded.
Does anybody know how I can fix it, so that free-text search from the Discover pane or from the APM pane starts working again?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论