-
Notifications
You must be signed in to change notification settings - Fork 2k
Open
Labels
discoverIssues related to Teleport DiscoverIssues related to Teleport Discoverfeature-requestUsed for new features in Teleport, improvements to current should be #enhancementsUsed for new features in Teleport, improvements to current should be #enhancements
Description
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
Labels
discoverIssues related to Teleport DiscoverIssues related to Teleport Discoverfeature-requestUsed for new features in Teleport, improvements to current should be #enhancementsUsed for new features in Teleport, improvements to current should be #enhancements