@SergeyKanzhelev i wrote to hellosign support and they told me that "something unknown went wrong". I need cncf to resend the agreement, but cncf support is not answering me, i can't find a way to do it through web interface. Is there a way to reach somebody who can resend me the agreement?
Hi is this a good place to ask for recommendation on implementing tracing in a company?
@jmichalek132 - this is a big question but feel free to ask. There are many experts here indeed :)
In our company we are debating how to start instrumenting applications, whether to start with few business operation and instrument them end to end or start by instrumenting at the application level (i.e. one span for a application) but for all methods
Which technologies / languages?
as for the technologies that would be a lot longer list
I would see - whatever you choose to use - if it supports auto instrumentation keeping the amount of monitoring code in your application as low as possible. OpenTelemetry is currently moving in that direction. Node.js already auto-instruments http and grpc ootb for instance.
I hate to say it but Gitter mobile app is so horrible. I really wish we stuck with slack.
I also just discovered I was kicked out of this room.
Everyone was kicked out of this room, because it was deleted.
@tylerbenson we never actually switched to slack, but we still could if we resolve the issues that were raised last time.
isn't slack clamping down on publicly joinable slacks?
or is there a paid cncf/linux foundation slack? since also if we did go to the trouble of moving I'd suggest doing so to a service we can keep history
There is a paid CNCF account, but we did not want to use a CNCF-wide shared account, as discoverability is bad enough given how many channels we need. K8s uses their own slack for this reason.
The other issues are the ones you mentioned: a lack of message retention, and difficulty for new users to join.
I’d argue that the tradeoff with gitter is difficulty for regular users to use every day.
I can’t remember if we determined whether a slack bot which archived everything was feasible or not.
@davidbarsky :wave: I'd definitely be interested in something like an OpenTracing Rust SIG. I've been holding off on add tracing to our Rust services since nothing there exists yet, and might have some time in the coming quarters to spend on that (thanks to @akvanhar for calling this Gitter to my attention)
@samschlegel i know someone implemented a mutex’d honeycomb subscriber a few days ago, and we just landed json support as well. it might be more than you’d expect!
exporter, sorry—terminology is hard to track :)
should have a lock-free span registry Soon™
(maybe this or next week, eliza’s fuzzing it)
Alyson van Hardenberg
lemme track down the honeycomb one and point you at the JSON-based one.
@tsloughter understood! what'd be the best way for me to provide specific feedback?
@davidbarsky I'll get back to you on that :). my current plan is to write up a starting point of sorts and then send it to you and a few others which we can then discuss and extend. the starting point will be examples of language to change and how I think they would be better described. i.e. what does having a Factory mean to the end user developer, what it allows described in a agnostic way