Class NoOpSpanFactory
- All Implemented Interfaces:
SpanFactory
SpanFactory implementation that creates a NoOpSpanFactory.NoOpSpan. This span does not do any tracing at all. It's
used as a fallback when there is no tracing implementation available, so framework code does not have to check.- Since:
- 4.6.0
- Author:
- Mitchell Herrijgers
-
Nested Class Summary
Nested Classes -
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final NoOpSpanFactorySingleton instance of theNoOpSpanFactory, which is used for configuration when there is no specific implementation configured. -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptioncreateDispatchSpan(Supplier<String> operationNameSupplier, Message parentMessage, Message... linkedSiblings) createHandlerSpan(Supplier<String> operationNameSupplier, Message parentMessage, boolean isChildTrace, Message... linkedParents) createInternalSpan(Supplier<String> operationNameSupplier) Creates a newSpanlinked to the currently active span.createInternalSpan(Supplier<String> operationNameSupplier, Message message) Creates a newSpanlinked to the currently active span.createRootTrace(Supplier<String> operationNameSupplier) Creates a newSpanwithout any parent trace.<M extends Message>
MpropagateContext(M message) Propagates the currently active trace and span to the message.voidRegisters an additionalSpanAttributesProviderto the factory.Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.axonframework.messaging.tracing.SpanFactory
createChildHandlerSpan, createLinkedHandlerSpan
-
Field Details
-
INSTANCE
Singleton instance of theNoOpSpanFactory, which is used for configuration when there is no specific implementation configured.
-
-
Constructor Details
-
NoOpSpanFactory
public NoOpSpanFactory()
-
-
Method Details
-
createRootTrace
Description copied from interface:SpanFactoryCreates a newSpanwithout any parent trace. This should be used for logical start point of asynchronous calls that are not related to a message. For example snapshotting an aggregate.In monitoring systems, this Span will be the root of the trace.
- Specified by:
createRootTracein interfaceSpanFactory- Parameters:
operationNameSupplier- Supplier of the operation's name.- Returns:
- The created
Span.
-
createHandlerSpan
public Span createHandlerSpan(Supplier<String> operationNameSupplier, Message parentMessage, boolean isChildTrace, Message... linkedParents) Description copied from interface:SpanFactoryCreates a newSpanlinked to asynchronously handling aMessage, for example when handling a command from Axon Server. The message attributes will be added to the span, based on the providedSpanAttributesProvidersfor additional debug information.In monitoring systems, this Span will be the root of the trace.
The message's name will be concatenated with the
operationName, seeSpanUtils.determineMessageName(Message).- Specified by:
createHandlerSpanin interfaceSpanFactory- Parameters:
operationNameSupplier- Supplier of the operation's name.parentMessage- The message that is being handled.isChildTrace- Whether to force the span to be a part of the current trace. This means not linking, but setting a parent.linkedParents- Optional parameter, providing this will link the provided message(s) to the current, in addition to the original.- Returns:
- The created
Span.
-
createDispatchSpan
public Span createDispatchSpan(Supplier<String> operationNameSupplier, Message parentMessage, Message... linkedSiblings) Description copied from interface:SpanFactoryCreates a newSpanlinked to dispatching aMessage, for example when sending a command to Axon Server. The message attributes will be added to the span, based on the providedSpanAttributesProvidersfor additional debug information.In monitoring systems, this Span will be part of another trace.
Before asynchronously dispatching a message, add the tracing context to the message, using
SpanFactory.propagateContext(Message)to the message's metadata.The message's name will be concatenated with the
operationName, seeSpanUtils.determineMessageName(Message).- Specified by:
createDispatchSpanin interfaceSpanFactory- Parameters:
operationNameSupplier- Supplier of the operation's name.parentMessage- The message that is being handled.linkedSiblings- Optional parameter, providing this will link the provided messages to the current.- Returns:
- The created
Span.
-
createInternalSpan
Description copied from interface:SpanFactoryCreates a newSpanlinked to the currently active span. This is useful for tracing different parts of framework logic, so we can time what has the most impact.In monitoring systems, this Span will be part of another trace.
- Specified by:
createInternalSpanin interfaceSpanFactory- Parameters:
operationNameSupplier- Supplier of the operation's name.- Returns:
- The created
Span.
-
createInternalSpan
Description copied from interface:SpanFactoryCreates a newSpanlinked to the currently active span. This is useful for tracing different parts of framework logic, so we can time what has the most impact.The message supplied is used to provide a clearer name, based on
SpanUtils.determineMessageName(Message), and to add the message's attributes to the span.In monitoring systems, this Span will be part of another trace.
- Specified by:
createInternalSpanin interfaceSpanFactory- Parameters:
operationNameSupplier- Supplier of the operation's name.- Returns:
- The created
Span.
-
registerSpanAttributeProvider
Description copied from interface:SpanFactoryRegisters an additionalSpanAttributesProviderto the factory.- Specified by:
registerSpanAttributeProviderin interfaceSpanFactory- Parameters:
supplier- The provider to add.
-
propagateContext
Description copied from interface:SpanFactoryPropagates the currently active trace and span to the message. It should do so in a way that the context can be retrieved by theSpanFactory.createLinkedHandlerSpan(Supplier, Message, Message[])method. The most efficient method currently known is to enhance the message's metadata.Since messages are immutable, the method returns the enhanced message. This enhanced message should be used during dispatch instead of the original message.
- Specified by:
propagateContextin interfaceSpanFactory- Type Parameters:
M- The message's type.- Parameters:
message- The message to enhance.- Returns:
- The enhanced message.
-