Bug
LogPipeline processing is ONLY wired in OtelLogsIngestService (OTLP endpoint /otlp). The syslog endpoint /syslog/v1/logs uses SyslogIngestService which has NO LogPipeline call. All syslog-ingested data bypasses the pipeline entirely.
Where
App/FeatureSet/Telemetry/Services/SyslogIngestService.ts
Missing:
- Import:
import LogPipelineService, { LoadedPipeline } from "./LogPipelineService";
- Pipeline loading at start of
processSyslogAsync()
LogPipelineService.processLog() call before dbLogs.push()
Reproduction
- Deploy OneUptime v10.8.2
- Create a LogPipeline with a CategoryProcessor that adds
log.category attribute
- Send syslog data to
/syslog/v1/logs
- Check ClickHouse:
attributes['log.category'] is always NULL for syslog-ingested logs
- Same pipeline works for OTLP-ingested logs (
/otlp)
Impact
Syslog is the primary ingestion method for many deployments. Without this, LogPipeline doesn't work for the most common log source.
Environment
OneUptime v10.8.2 Community Edition, Docker Compose.
Bug
LogPipeline processing is ONLY wired in
OtelLogsIngestService(OTLP endpoint/otlp). The syslog endpoint/syslog/v1/logsusesSyslogIngestServicewhich has NO LogPipeline call. All syslog-ingested data bypasses the pipeline entirely.Where
App/FeatureSet/Telemetry/Services/SyslogIngestService.tsMissing:
import LogPipelineService, { LoadedPipeline } from "./LogPipelineService";processSyslogAsync()LogPipelineService.processLog()call beforedbLogs.push()Reproduction
log.categoryattribute/syslog/v1/logsattributes['log.category']is always NULL for syslog-ingested logs/otlp)Impact
Syslog is the primary ingestion method for many deployments. Without this, LogPipeline doesn't work for the most common log source.
Environment
OneUptime v10.8.2 Community Edition, Docker Compose.