Errors in elastalert logs related to built-in detections #13612
-
Version2.4.100 Installation MethodSecurity Onion ISO image Descriptionconfiguration Installation TypeStandalone Locationon-prem with Internet access Hardware SpecsExceeds minimum requirements CPU48 RAM512G Storage for /445.07 GiB Storage for /nsm11.64 TiB Network Traffic Collectiontap Network Traffic SpeedsLess than 1Gbps StatusYes, all services on all nodes are running OK Salt StatusNo, there are no failures LogsYes, there are additional clues in /opt/so/log/ (please provide detail below) DetailI'm seeing a lot of ERROR-level logs in These errors are related to default (built-in, not custom) detections in I'm not using elastic agents nor any other methods of importing data/logs from Windows or any other OS. I'm wondering if these errors are ignorable, concern-worthy, and/or able to be squelched?
Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
This issue persists in 2.4.110 |
Beta Was this translation helpful? Give feedback.
-
@TheRealPancakes Some of these are expected. With the move to EQL, Elasticsearch does a pre-check on the EQL query - if the query targets fields that don't have any mappings, it will fail the precheck with an error. That is what the The others are Sigma field mappings issues - we are actively working on those. |
Beta Was this translation helpful? Give feedback.
@TheRealPancakes Some of these are expected. With the move to EQL, Elasticsearch does a pre-check on the EQL query - if the query targets fields that don't have any mappings, it will fail the precheck with an error. That is what the
unknown_column
errors are. Annoying, but not indicative of a deeper issue.The others are Sigma field mappings issues - we are actively working on those.