Skip to content
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

Dashboard errors on httpRequest.clientIp after install #2

Open
pkennedyvt opened this issue Jul 24, 2020 · 3 comments
Open

Dashboard errors on httpRequest.clientIp after install #2

pkennedyvt opened this issue Jul 24, 2020 · 3 comments

Comments

@pkennedyvt
Copy link

The first index that is built has cleintIp as text. This throws the following error in the Dashboard:

Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Fielddata is disabled on text fields by default. Set fielddata=true on [httpRequest.clientIp] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead."}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"awswaf-2020-07-23","node":"YRRPzsdTRNKcReVxFSbKwA","reason":

Two things fix it.

  • When a second index is built clientIp becomes a keyword. I think this is coming from aws-waf-dashboard/cloudformation-custom-resources/kibana-customizer-lambda/custom/template.json.
  • Changing the three saved objects of Top10 IpAddresses, Filters and Unique IP count to have "field": "httpRequest.clientIp.keyword" in visiState instead of just "httpRequest.clientIp".
@Mudpuppy12
Copy link

This change worked for me

@Galal-Eltfawy
Copy link

@Mudpuppy12 how did you solve it , would you please share the modified file template.json

@dkennedy256
Copy link

How do you fix this?

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

No branches or pull requests

4 participants