A common issue with intervalmatch is fields that are automatically recognised with as a timestamp do not work correctly when trying to perform an interval match.

Never fear! You can use untag to force remove the $timestamp to make it recognise the date time field as a number - this means it will actually work in an intervalmatch.

EventLog:
Load
num("time") as Time,
tag as Event,
svalue as Comment
FROM [lib://Dfile/DATA.csv] (txt, codepage is 28591, embedded labels, delimiter is ',', msq)
WHERE match(svalue, 'ACTIVE', 'Running')>0 or wildmatch(tag, '*channel1_AlarmMessage')>0;

OrderLog:
Load
//RecordID,
//"time" as [Original Time],
num(mintime) as Start,
num(maxtime) as End,
1 as Order;
//tag,
//svalue;
Load
recno() as RecordID,
"time",
"time" + -0.00034722221666 as maxtime,
"time" - -0.00034722221666 as mintime,
tag,
svalue
FROM [lib://Dfile/DATA.csv] (txt, codepage is 28591, embedded labels, delimiter is ',', msq)
WHERE match(svalue, 'FEED_HOLD','INTERUPTED')>0;

Untag field Time, Start, End with $timestamp;

How about them apples?