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

VMWARE_SEV_CURRENT : Document contains at least one immense term in field #18

Closed
marcolefo opened this issue Nov 17, 2023 · 2 comments
Closed

Comments

@marcolefo
Copy link

marcolefo commented Nov 17, 2023

Hi

Like in #17
but for VMWARE_SEV_CURRENT

Perharps it's because we have vcenter 8 ?

  • Graylog 5.2.1
  • Opensearch 2.11.0
  • vcenter 8.0.2
  • ESXi 7.0.3

Complete error message
OpenSearchException[OpenSearch exception [type=illegal_argument_exception, reason=Document contains at least one immense term in field="VMWARE_SEV_CURRENT" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[115, 99, 97, 112, 105, 46, 118, 109, 119, 97, 114, 101, 46, 99, 111, 109, 32, 116, 105, 109, 101, 100, 32, 111, 117, 116, 46, 32, 40, 99]...', original message: bytes can be at most 32766 in length; got 63018]]; nested: OpenSearchException[OpenSearch exception [type=max_bytes_length_exceeded_exception, reason=bytes can be at most 32766 in length; got 63018]];

Extractor configuration
Extractor type: Regular expression
Source field: message
Regular expression: to (.*)]

@dcecchino
Copy link
Owner

image

Delete the grok VMWARE_SEV_CURRENT extractor and create a new Regular expression called VMWARE_SEV_CURRENT

@marcolefo
Copy link
Author

Thanks

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

2 participants