[
https://issues.apache.org/jira/browse/TINKERPOP-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296339#comment-17296339
]
Stephen Mallette edited comment on TINKERPOP-2506 at 3/5/21, 9:00 PM:
----------------------------------------------------------------------
sorry - i'd not noticed the part where you had wanted feedback on this issue.
offhand, i can't think of a reason why the status could not be exposed for
reading. if you'd like to submit a PR for review that would be nice. thank you.
was (Author: spmallette):
sorry - i'd not noticed the part where you had wanted feedback on this issue.
offhand, i can't think of a reason why the status could not be exposed for
reading.
> Expose client WebSocket connection status
> -----------------------------------------
>
> Key: TINKERPOP-2506
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2506
> Project: TinkerPop
> Issue Type: Improvement
> Components: javascript
> Reporter: Ebrahim
> Priority: Minor
>
> The WebSocket connection status is a critical piece of info when implementing
> readiness/liveliness probes in kubernetes deployment scenarios. Currently the
> connection status is kept internally in the `Connection` class and not
> accessible from outside.
> [https://github.com/apache/tinkerpop/blob/332177a4b65563bc9ac2ad89e1a3ce78bf290195/gremlin-javascript/src/main/javascript/gremlin-javascript/lib/driver/connection.js#L96]
>
> Please let me know if this makes sense and I can send a PR.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
