Skip to content
This repository has been archived by the owner on Jun 8, 2023. It is now read-only.

failure in bulk execution #13

Open
adrwh opened this issue Jun 25, 2020 · 2 comments
Open

failure in bulk execution #13

adrwh opened this issue Jun 25, 2020 · 2 comments

Comments

@adrwh
Copy link

adrwh commented Jun 25, 2020

Hello, i am using Elastic Cloud, 7.8.0, and getting this failure in Cloudwatch logs.

failure in bulk execution:
[0]: index [cloudflare], type [doc], id [null], message [ElasticsearchException[Elasticsearch exception [type=illegal_argument_exception, reason=field [ClientRequestProtocol] not present as part of path [ClientRequestProtocol]]]]

I can see this in the ingest pipelines

{
      "dissect": {
        "field": "ClientRequestProtocol",
        "pattern": "HTTP/%{http.version}"
      }
    },
    {
      "rename": {
        "field": "ClientRequestProtocol",
        "target_field": "cloudflare.client.request.protocol",
        "ignore_missing": true
      }
    }

and this in the index template as a field

"cloudflare.client.request.protocol" : {
            "type": "keyword"
         }

Everything here looks "fine" i think..

Please help.

@adrwh
Copy link
Author

adrwh commented Jun 25, 2020

Update: I can confirm that the Cloudflare logs do not include the ClientRequestProtocol in the source data.

I removed the fields from the template and daily and weekly ingest pipelines and was able to send a test log entry successfully using the cli.

Is this a bug somewhere?

@lag13
Copy link

lag13 commented Jul 9, 2020

I believe they need to add the "ignore_missing": true to the dissect processor as well, doing that fixed this issue for me. I personally have seen ClientRequestProtocol come through in my logs which is why I didn't want to remove it from my pipeline.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants