[
https://issues.apache.org/jira/browse/TINKERPOP-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312224#comment-17312224
]
Clément de Groc commented on TINKERPOP-2523:
--------------------------------------------
Ideally, if we could also record the same information TinkerPop provides in its
Profile step in OpenTracing (/OpenTelemetry), that would be great.
There are certainly other road blockers, but if {{MutableMetrics}} recorded the
start/end time instead of duration, then we could maybe construct OpenTracing
spans from them?
> Allow registration of listeners for traversal iteration begin/end events
> ------------------------------------------------------------------------
>
> Key: TINKERPOP-2523
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2523
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.4.10
> Reporter: Clément de Groc
> Priority: Minor
>
> In order to improve observability/monitoring (e.g. distributed tracing,
> logging of traversals requests), it would be nice if users could register
> custom listeners for traversal iteration begin/end events.
> Those begin/end events are actually already nicely exposed as protected
> methods in
> [TraversalOpProcessor|https://github.com/apache/tinkerpop/blob/master/gremlin-server/src/main/java/org/apache/tinkerpop/gremlin/server/op/traversal/TraversalOpProcessor.java#L262-L272].
> Though, in 3.4.10, it is difficult to subclass TraversalOpProcessor to
> override those methods as the
> [OpLoader|https://github.com/apache/tinkerpop/blob/master/gremlin-server/src/main/java/org/apache/tinkerpop/gremlin/server/op/OpLoader.java#L47]
> ensures only one OpProcessor can be loaded with name "traversal".
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
