eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkxpYW0gRmFsbG9uIiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IkxpYW0gRmFsbG9uIiwibGFuZ3VhZ2UiOiJlbiIsImRpYWdyYW1EaXNwbGF5TmFtZSI6IiIsInNGaWxlSWQiOiIiLCJhdHRJZCI6IjEzODg3MzAyMSIsImRpYWdyYW1OYW1lIjoiVHlwaWNhbCBUZXN0IENvbXBvc2l0aW9uIiwiYXNwZWN0IjoiIiwibGlua3MiOiJhdXRvIiwiY2VvTmFtZSI6IlRlc3QgYW5kIFZlcmlmaWNhdGlvbiBvZiBBQ00gU3RhdGUgTWFuYWdlbWVudCIsInRic3R5bGUiOiJ0b3AiLCJjYW5Db21tZW50IjpmYWxzZSwiZGlhZ3JhbVVybCI6IiIsImNzdkZpbGVVcmwiOiIiLCJib3JkZXIiOnRydWUsIm1heFNjYWxlIjoiMSIsIm93bmluZ1BhZ2VJZCI6MTM4ODczMDE5LCJlZGl0YWJsZSI6ZmFsc2UsImNlb0lkIjoxMzg4NzMwMTksInBhZ2VJZCI6IiIsImxib3giOnRydWUsInNlcnZlckNvbmZpZyI6eyJlbWFpbHByZXZpZXciOiIxIn0sIm9kcml2ZUlkIjoiIiwicmV2aXNpb24iOjEsIm1hY3JvSWQiOiJhMDg4MjczZC00NGQ0LTQ4ZGUtOTBkMy00ZjY4YTVlYzNjM2IiLCJwcmV2aWV3TmFtZSI6IlR5cGljYWwgVGVzdCBDb21wb3NpdGlvbi5wbmciLCJsaWNlbnNlU3RhdHVzIjoiT0siLCJzZXJ2aWNlIjoiIiwiaXNUZW1wbGF0ZSI6IiIsIndpZHRoIjoiNzExIiwic2ltcGxlVmlld2VyIjpmYWxzZSwibGFzdE1vZGlmaWVkIjoxNjU3NzA1NzE5MDAwLCJleGNlZWRQYWdlV2lkdGgiOmZhbHNlLCJvQ2xpZW50SWQiOiIifQ==
The diagram above shows a typical test Automation Composition
The Microservice is a test microservice that comes up in Kubernetes and it can be configured over HTTP to:
- Send events periodically on a topic
- Receive and count events it receives on a topic
- Forward events that it received on one topic onto another topic
- Count the events it sends/receives and report that count over Prometheus using standard ACM counters in the participant intermediary