> but every vendor still finds a way to pull you into their proprietary query dialect We just finished adding support for OTel in our own product, and from the "vendor" side, I think there are two reasons for this. The…
Since this is an OTel-related submission, you could also use OTel collectors to collect and forward logs to a central OTel collector instance. > yes it doesn’t solve the UI problem for those, but it does solve…
>> This terrified the Swift compiler engineers, they were worried that untested complier pass orders would expose untested bugs > This would scare me too. FWIW, I made it clear that this was also a great way to break…
> They had negative nine figures of (profit). FTFY
> but every vendor still finds a way to pull you into their proprietary query dialect We just finished adding support for OTel in our own product, and from the "vendor" side, I think there are two reasons for this. The…
Since this is an OTel-related submission, you could also use OTel collectors to collect and forward logs to a central OTel collector instance. > yes it doesn’t solve the UI problem for those, but it does solve…
>> This terrified the Swift compiler engineers, they were worried that untested complier pass orders would expose untested bugs > This would scare me too. FWIW, I made it clear that this was also a great way to break…
> They had negative nine figures of (profit). FTFY