Skip to content

Expose connection state to client consumers #29

Description

@aalexandrov

Is your feature request related to a problem? Please describe.

At Materialize, we plan to use LaunchDarkly in continuously running processes and would like to have an internal metric indicating a state where the client instance temporary could not communicate with the LaunchDarkly service.

Describe the solution you'd like

Some method on the client instance that returns a bool or an enum indicates whether the client is connected and the connection is alive.

Describe alternatives you've considered
Periodically polling LaunchDarkly API in a separate process / Tokio task.

Additional context

As a cloud service that is meant to be used in critical business applications, it is important to have good visibility for all our external dependencies.

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