Just a nit, for Facebook, Scuba is not the logging ingestion service. It's Scribe, which Scuba itself uses as the ingestion :)
https://engineering.fb.com/2019/10/07/data-infrastructure/sc...
(I worked in Scribe)
https://engineering.fb.com/2019/10/07/data-infrastructure/sc...
(I worked in Scribe)
The main issue (as usual in big companies) is the large amount of inter-dependencies with internal systems. Scribe as-is today doesn't make much sense outside Facebook. And yeah, it could be cleaned up, mock the internal services and OSS it. But that's a lot of work, both doing it and maintaining it. And having all those mocks, etc "wouldn't be Scribe as-is either"in terms of how e.g. it scales and so on.
In any case, the storage (LogDevice, https://github.com/facebookarchive/LogDevice) which is a large part of the system was open sourced a while back and... sadly it went again into "not-maintained OSS".
Finally, you can get a similar-ish system working with OSS tools (e.g. fluentd + Kafka) that will also scale quite well and which IMHO can also made to scale to Facebook-size levels. So, the incentive is there, but there are OSS alternatives already available :)
The internal improvements aren't interesting or available to anyone outside of facebook.
The open source version is creaky and very difficult to drag forward to newer versions of thrift.
So -- thanks Facebook for dropping weird artifacts like the aftermath of Roadside Picnic. Woe unto all who adopt these soon-to-be-orphaned technologies.