A little off topic, but if you are going with mostly managed services and you don't use k8s, what would you do to have decent tracing and observability? I'm currently using a combination of FaaS and cloud queues, for example.
Open sourcing Pixie under Apache 2.0 license
11–20 of 21 posts
Re: Open sourcing Pixie under Apache 2.0 license
#12Presumably a completely different Pixie from the open-source one at https://sourceforge.net/projects/pixie/ ?
When I saw Pixie my first thought was the component of PIX[0] which installs itself on the Xbox.
Re: Open sourcing Pixie under Apache 2.0 license
#13Presumably a completely different Pixie from the open-source one at https://sourceforge.net/projects/pixie/ ?
It's interesting to see these names which are used by several projects. When I saw Pixie my first thought was the component of PIX[0] which installs itself on the Xbox. [0] https://devblogs.microsoft.com/pix
Re: Open sourcing Pixie under Apache 2.0 license
#14A little off topic, but if you are going with mostly managed services and you don't use k8s, what would you do to have decent tracing and observability? I'm currently using a combination of FaaS and cloud queues, for example.
Have you looked into instrumenting zipkin or opentracing? I instrumented zipkin in a Java project and found it generally pretty easy
Disclaimer: I am one of the maintainers of SigNoz
Re: Open sourcing Pixie under Apache 2.0 license
#15Presumably a completely different Pixie from the open-source one at https://sourceforge.net/projects/pixie/ ?
Re: Open sourcing Pixie under Apache 2.0 license
#16Re: Open sourcing Pixie under Apache 2.0 license
#17Presumably a completely different Pixie from the open-source one at https://sourceforge.net/projects/pixie/ ?
Re: Open sourcing Pixie under Apache 2.0 license
#18Having just seen JBD from AWS mention now working on this project full time my complete assumption is that AWS will offer it as a service and this isn't possible if the licensing goes in the direction of blocking commercialisation. Since the startup that was building this got acquired by New Relic and Peter Fenton serves on that board I assume they're trying to attack this strategically in a different way. If that's…
Re: Open sourcing Pixie under Apache 2.0 license
#19Having just seen JBD from AWS mention now working on this project full time my complete assumption is that AWS will offer it as a service and this isn't possible if the licensing goes in the direction of blocking commercialisation. Since the startup that was building this got acquired by New Relic and Peter Fenton serves on that board I assume they're trying to attack this strategically in a different way. If that's…
So, does that mean that AWS and New Relic can both offer a cloud version of Pixie. In that case, won't that be a bad deal for New Relic - since they acquired Pixie?
Re: Open sourcing Pixie under Apache 2.0 license
#20Earlier quoted context omitted.
And your CLA [1] does not reassign copyright, ensuring that you can't re-license later. Good on you! [1]: https://github.com/pixie-labs/pixie/blob/main/CLA.md
The CLA gives permission to sublicense, but it isn't clear to me if this allows proprietary relicensing or not.
> We agree to license the Contribution only under the terms of the license or licenses which We are using on the Submission Date for the Material