Skip to content

[Heartbeat] Support for multiple status codes #13595

@andrewvc

Description

@andrewvc

Right now heartbeat assumes that a service has a single HTTP status code representing its up state. In this forum thread we found that isn't the case in the real world.

I propose we allow check.response.status to take an array of codes as an argument to better handle this situation. While it's not ideal, this is a real situation operators may find themselves in.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions