Replies: 1 comment 6 replies
-
@jacum thanks for your interest. We are being very conservative about what goes into Apache Pekko v1.0.0. Basically, it is based on the most recent Apache licensed Akka releases. Nothing else gets added. We are just changing package names, jar names, docs, etc to reflect the move to ASF. For a v1.1.0 release, we will consider extra changes. This subsequent release feels like it won't happen for quite some time based on current v1.0.0 velocity. There are a lot of modules that Pekko team need to maintain. Is there a reason, why a 'Pekko Sensors' could not remain a separate project - at least for the time being? It is just my opinion, but I would prefer to make changes to Pekko core that make external ecosystem libs easier to write and maintain - as opposed to bringing them all in-house. I have https://github.com/pjfanning/micrometer-akka and I'm considering creating a pekko version but not to bring it into Pekko. But if 'Pekko Sensors' were to look like a better bet, I might abandon 'Micrometer-Pekko'. Does this make sense? |
Beta Was this translation helpful? Give feedback.
-
Ladies and gentlemen,
I am the author and maintainer of Akka Sensors (https://github.com/jacum/akka-sensors) library, native Prometheus monitors for Akka and around. It is an alternative to Lightbend Cinnamon and open-source Kamon and currently used in production at the Dutch ING bank and OnAir Entertainment. Not a 100% Cinnamon drop-in replacement (cluster features aren't covered) - but gives quite useful insights nevertheless.
Would it make sense to include it as a standard part for Pekko, to give potential Akka users switching to Pekko at least something, instead of Cinnamon (part of paid Lightbend license, not available for Pekko users). It also opens a way to further development of built-in instrumentations, e.g. cluster features.
Beta Was this translation helpful? Give feedback.
All reactions