LogPipeline: GrokParser processor type defined but not wired

[netmstnet]

Bug

The GrokParser processor type is defined in LogPipelineProcessorType with full configuration interface (GrokParserConfig), and users can create GrokParser processors via UI or API. But the applyProcessor() switch in LogPipelineService.ts does NOT handle LogPipelineProcessorType.GrokParser — it falls through to default: return logRow;.

Where

App/FeatureSet/Telemetry/Services/LogPipelineService.ts line 183:

switch (processor.processorType) {
  case LogPipelineProcessorType.AttributeRemapper: ...
  case LogPipelineProcessorType.SeverityRemapper: ...
  case LogPipelineProcessorType.CategoryProcessor: ...
  default:
    return logRow;  // <- GrokParser falls here, does nothing
}

Impact

• No grok library imported (no @silius/grok, no oniguruma)
• No applyGrokParser() method
• Users can create GrokParser processors that silently do nothing
• UI allows creating them without warning that they're non-functional

Expected

Either:

1. Implement GrokParser with a grok library, OR
2. Hide GrokParser from the UI until implemented, OR
3. Show a warning when creating GrokParser processors

Environment

OneUptime v10.8.2 Community Edition.