-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Internal server error: Compressor detection can only be called ... #63726
Comments
The second line of error indicates that this could be related to the |
I'm not sure if I understand what do you mean by "manually"... would you like me to write the agent configuration on host? |
No, what I meant is trying to load this ingest pipeline here into Elasticsearch through the Elasticsearch API: https://github.com/elastic/package-registry/pull/323/files#diff-c78e2000afa7f358aa9cdfa6c1a21d1c Curious to see if it succeeds or fails. |
Pinging @elastic/ingest-management (Team:Ingest Management) |
There is currently a problem sending YAML pipelines to elasticsearch. I'm investigating. |
@ruflin So when I try to
with |
@mtojek Could you try with a pipeline definition that starts with
Also, I'm not sure about the empty lines, as yaml seems to be really sensitive to whitespace. You can use this curl command to test if a pipeline is valid (note the use of
|
Sure, I can try to do this, but this file is identical with the original one in Beats (https://github.com/elastic/beats/blob/787dd62af155999dd3b9a65a532b01c9439318ee/filebeat/module/mysql/error/ingest/pipeline.yml). I do not convert in any way. Adding |
Interesting. Now I'm wondering why Beats itself can load it. Could you check in the pipeline loading code if we do any magic there. I remember some discussion in ECS that each yaml should start with a |
It took me a while, but I managed to go through the follow. The Beats application unmarshals the YAML or JSON files using standard Hmm... I will add |
Lol, so we actually load JSON from Beats 🤦 ++ on adding |
Closing this in favour of elastic/package-registry#404 and #64739 |
I enabled the IngestManager plugin and tried to save a data source. Unfortunately it ended up with the following exception:
I used SNAPSHOT versions of Kibana and Elasticsearch. Ones, available in elastic/package-registry#351
/cc @ruflin
The text was updated successfully, but these errors were encountered: