Skip to main content
Panther Knowledge Base

How do I resolve the error "Field validation failed on the 'required' tag" in Panther?

ISSUE

 The following error appears on a log source in the Panther Console:

Error:Field validation for '<Field>' failed on the 'required' tag

This error can appear for supported logs or custom logs.

How do I resolve this error? Once I resolve it, how can I re-ingest the failed logs?

RESOLUTION


To troubleshoot the error:

  1. In the Panther Console, click Configure > Log Sources on the left sidebar.
  2. Click the log source name, then click the Schemas tab to navigate to the log source's schema definition.
  3. Locate the field for which the error message is returned.
    • For example, if the error message contains the reference Field_4_Ip, then you can look for a field named ip in your schema.
  4. Identify whether this field is declared as required, as shown in the example below:
     name: ip
      required: true
      type: string
  5. If the field is required, check the raw events that are causing the error message to appear. The most probable scenario is that this field is missing from the raw events.
  6. If the field is not always present in the raw events that are coming to your log source, then you can remove the required flag from the statement in the schema and modify it as shown in the example below:
    - name: ip
      type: string
  7. After removing the required flag, check to see if the events are arriving without causing the error message.

If everything seems as expected, then you're good to go! If not, you can always contact Panther Support.

Re-ingesting the failed logs

The failed logs are not automatically re-ingested. For this purpose, we have this article from our KB that describes how to backfill logs into Panther: Can I backfill the logs of a new log source into Panther?

Note: Duplications might be created if some of the backfilled events of a file have already been ingested without issues.

 

CAUSE

Τhis error message indicates that a required field in the schema definition is missing from the raw events that were ingested.