Synthetic Transactions

preview_player
Показать описание
An Architects View of an Important Monitoring Approach, the measurement of user goals via synthetic transactions.

Table of Contents:

00:00 - Synthetic Transactions
00:09 - Problem Statement
02:01 - Definition
02:31 - Goals of Synthetic Transactions
04:06 - Where do STs come from?
05:39 - Nomenclature – Business Processes
12:37 - Requirements to implement STs
16:37 - Metadata as unified log streams
17:38 - Example (as JSON)
19:02 - Serialized Log Streams are the Journey from E2E
19:49 - Yielding a journal by transaction
20:26 - What can the data yield?
24:05 - About Me
Рекомендации по теме
Комментарии
Автор

Stuart, excellent introduction to ST. Thank you! I have been in a huge and extremely important project a few years ago and our Chief Architect introduced a so called "Correlation ID" which was generated by the FE and travelled all way through the system to the data store. This solution looks like a ST implementation for me. But what is bothering me is that you seem to suggest that ST are NOT to be used for REAL business activities but rather they represent kind of "fake" little things to check the system from end to end. Now my question: "Why not to make a ST a part of the "official" business processes for ALL activities?" What is wrong with that? Please, elaborate. NOTE: You can elaborate over the next class. :-)

alexgordon