QuestionQ9

VerifiedParsing and Normalization

You clone a default parser and change only the parseTimestamp() function to support a custom time format in your logs.

What effect does this have on queries that search this data?

Explanation

In Falcon LogScale, the built-in #type field identifies the parser that processed the log. A cloned parser has a distinct parser identity even when its parsing logic differs only in parseTimestamp(), so searches constrained by #type must be updated to match the cloned parser. #Cps.version denotes the CPS standard targeted by the parser and does not change merely because timestamp parsing is customized. LogScale Data Ingestion Overview, CPS-Compliant Parsers

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!