[filestream] - input being degraded even if context is cancelled

[VihasMakwana]

We have a faulty piece of code at

beats/filebeat/input/filestream/input.go

Lines 169 to 172 in c3571bf

	if err := inp.readFromSource(ctx, log, r, fs.newPath, state, publisher, metrics); err != nil {
	ctx.UpdateStatus(status.Degraded, fmt.Sprintf("error while reading from source: %v", err))
	return err
	}

We report input as DEGRADED on any error. However, we should not report degraded if context is cancelled.

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[lucabelluccini]

The drawback of this is Elastic Agents show up unhealthy on Fleet UI (as 1 or more units are not healthy), generating concerns on users.

[VihasMakwana]

@cmacknz what should be the best course of action here? We shouldn't report context canceled and mark agent as degraded, right?

i think we should filter such errors out while reporting degraded mode.

[cmacknz]

We shouldn't report context canceled and mark agent as degraded, right?

Correct as this likely isn't a real error and probably a side effect of shutting down or reloading.