Skip to content

Rationale for WARN taking precedence over STALE for the top_level_state #658

Description

@iamnambiar

In the aggregator code, WARN/ERROR takes precedence over STALE when computing the top_level_state. Was this an intentional design decision? If so, can I ask what was the reasoning behind it? I can understand ERROR taking precedence, but I am curious why WARN does as well. For example, a node that has stopped publishing entirely could be more critical than one that's still alive but reporting a warning, so I'm wondering what motivated this design.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions