I would like to propose that we create a SIG that will have as a primary goal to define the OpenTelemetry story for logs:
Thanks @bogdandrutu for starting this. I'd like to get involved in the SIG.
/CC @mtwo @c24t I know that this is something that also is interesting for you
/cc @obecny because you wrote the logging plugin for js
Sounds good to me! Feels like we are still desperate to get tracing and metrics out the door, but I'm happy to start the discussion.
@tedsuo I feel that we need just start discussion, and define some work that these people need to do. No ask for any commitment in terms of implementation work or specs yet.
We're extremely interested. I think that @flands is as well, and possibly @SergeyKanzhelev .
yep
+1
A couple more items for the new SIG charter:
I have recently put some thought into a few of these and I volunteer to be SIG's bootstrapper. If there are no objections I can create issues in relevant repos where we can discuss these and other log-related topics and also look into scheduling the first SIG meeting sometime after trace/metric Beta release.
Instead of issues, could we do a Google doc? Especially if you already have views/thoughts on those topics.
cc @otoolep, who works on cloud logging at Google and worked with me and @mtwo on OpenCensus logging.
Google doc works too. I'll start one.
@tigrannajaryan since you took a step to create this doc, I would suggest also to create an entry in the readme and add this SIG, schedule a meeting, and one of the topic should be also to determine the participants in the SIG (maybe in the first meeting?).
If it helps, here's @mtwo's doc from the OpenCensus logging work last year (copied to remove some internal comments).
Here is the Doodle to vote for the bootstap meeting slot: https://doodle.com/poll/sthbvs8niwwimpec
Bootstrap meeting vote complete, confirmed meeting time: Mar 18, 10am Pacific Time / 1pm Eastern Time.
Meeting added to OpenTelemetry calendar.
Zoom: https://zoom.us/j/8203130519
Agenda: https://docs.google.com/document/d/1cX5fWXyWqVVzYHSFUymYUfWxUK5hT97gc23w595LmdM/edit#heading=h.lro8kgalys10a
Most helpful comment
Google doc works too. I'll start one.