klarna-incubator / service_communication_map Goto Github PK

Currently we use rendering built in jgrapht library. It is ok for start or t keep it for general testing, but it would be nice to replace it with some visually nicer.
Maybe some Vaadin component, like https://vaadin.com/directory/component/graph-explorer-vaadin-7

Assume that when service A calls Service B, there is at least one unique ID in logs from service A and service B that allows to deduct that there is communication between A and B. Use that information to connect corresponding services in generated map.

1. update README
2. Add Java HelloWorld
3. add git ignore etc

Given raw input data (log lines) process them into a graph

• consider lots of lines -> streaming API
• parse log line to obtain timestamp
• parse log line to obtain service name
• map to graph data structure
• consider mapping to existing graph library, e.g. https://jgrapht.org/

For a specific flow, graph nodes should be shown in order of in which participate in a give flow. So graph layout algorithm should take first appearance (time based) of the node as the input, i.e. chronological order should be preserved.

For example wen flow was 1->2, 2->3, 2->4, 4->5
Order of nodes (either left to right, or top down, or whatever arbitrary direction) should be 1, 2, 3 and 4, 5, e.g.

1 -> 2 -> 3 
      \-> 4 -> 5

Need something that will read data input:

• allow to specify input log files location
• read one file
• read multiple files
• support only log per single line (no multi line parsing)
• assume larger files, streaming lines (or similar) solution would be needed
• have a way to pass read raw lines for further processing by other components

Wen doing new searches newly rendered graphs are getting appended to the DOM, but old ones stay.

This is a bug, it is expected for the old one(s) to be removed when new graph is generated.

Given graph structure represent it in visual way.

Potential candidates, PlantUML, Vaadin, Processing, etc.

This is first iteration. Start small. It is ok to change underlying presentation layer as needed.

Currently all code generated by Vaadin is checked in.

• remove checked in code
• add git ignore rules to avoid generated code from being checked in

extract more different IDs form code to improve building relations between services

log messages can contain up to multiple different IDs, extract them all to be able to derive relationship between them

affects #23