Represented by rectangles directly attached to arrow heads. N/A - currently it's not possible to collect telemetry data to visualize message handlers. It is immediately followed by its handler, which usually overlaps the handler that sent the loopback message. Represented by an arrow that connects back to the sending object's lifeline. Represented by a short uni-directional arrow that does not connect to another endpoint lifeline and a specific icon. Represented by a sloping dashed or solid line with an open arrow. N/A - all NServiceBus messages are asynchronous so the ServiceInsight sequence diagram has no special representation for asynchronous messages and no representation for synchronous messages, even though messages may exhibit synchronous behavior by design. Used for response messages and asynchronous messages. Used solely for synchronous send messages. Used solely to represent create messages and response messages. Used solely for send and request types of messages. Used to represent any type of message other than events, including response messages. Represented by an incoming message (gate) from outside the diagram. This representation is used because metadata about what precedes the sequence is unavailable. Represented by a black rectangle with a white "play" icon. However, due to technical limitations and specifics related to messaging systems, the sequence diagram in ServiceInsight has some notable differences: Item The language used in the sequence diagram is largely modeled after the standard defined by UML sequence diagrams. The sequence diagram does not currently support visualization of the time at which the timeout message was sent back, and will only indicate when it was processed. The time of processing may not correspond to the time at which a timeout message was sent back for processing by the timeout message scheduler. These arrows are shown in the order in which those messages were sent or published. If the endpoint received more than one message of that type, the specific message being processed may be seen by hovering over or selecting the processing box.Ī message arrow shown leaving a processing box represents an outgoing message that was sent or published while processing the incoming message. This is represented by a box on the endpoint lifeline labelled with the message type. Some time after a message is received, it is processed by the receiving endpoint. Right-clicking on a message label shows actions related to that message. The arrow always points from the sending endpoint to the receiving endpoint. When a message is sent, a solid arrow is drawn from the lifeline of the sending endpoint to the lifeline of the receiving endpoint, labelled with the message type. The diagram will show only the last 50 messages from the conversation, and this may not include the initiating message. It can also happen if the number of messages in the conversation is very large. This can happen if the conversation started a long time ago and the initiating message has expired. The Start of Conversation marker may not always be visible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |