Feedback on the OpenAPM initiative

[Alexander Wert]

Any feedback on the OpenAPM initiative is welcome!

[geis...@gmail.com]

This speeds up research into how the open source building blocks can fit together.

I can't figure out how to reproduce it, but at one point I got a diagram that had Prometheus feeding into Micrometer. That didn't make sense.

I find some of the metadata not nuanced enough. For example, the aspect "tracing [eum]" brings up Jaeger, Zipkin, Kamon, and OpenCensus. As far as I can tell, one could use these libraries build EUM, but they do not do anything to support EUM out of the box.

I'm trying to figure out an architecture that supports metrics, tracing, and logs, and is not too redundant. To help me, it would be nice to see labeled flow between components to indicate what kind of data is being transported in that model.

Thank you for the effort. This is useful and promising.

[filipemor...@gmail.com]

I agree with geis...@gmail.com, for example, it's missing Graylog, witch is easily integrated with icinga 2 and Logstash. 

The diagram really speedup the researches, but doesn't help on how to reproduce.

The lines connecting the blocks can have some info or hints on how to connect the blocks.

[Alexander Wert]

Thank you geis...@gmail.com, thank you filipe...@gmail.com!

Your feedback is very valuable for us to further improve the OpenAPM initiative!

Regarding missing components and tools: 

We are aware that the landscape is not exhaustive. But we aim at continuously enriching the landscape with more tool. 

We are adding more tools and also encourage everyone who is interested to contribute tool descriptions on https://github.com/openapm/landscape-model.