Skip to content

Capture fetcher errors as user tasks #62836

@Tener

Description

@Tener

What would you like Teleport to do?

Capture errors raised by fetchers and create appropriate user tasks from those.

Currently we limit ourselves to logs:

	if err != nil {
		if trace.IsNotFound(err) {
			return
		}
		slog.ErrorContext(context.Background(), "Failed to fetch instances", "error", err)
		return
	}

What problem does this solve?

Improves Discover UX. As it is, fetcher errors are not reflected at all in discovery config status which incorrectly makes it appear "healthy, but inactive".

If a workaround exists, please include it.

User needs to analyze discovery service logs to see the error even happened.

Metadata

Metadata

Assignees

No one assigned

    Labels

    discoverIssues related to Teleport Discoverfeature-requestUsed for new features in Teleport, improvements to current should be #enhancements

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions