# Agenda: Jun 19 WASI Observe Video call

- **Where**: zoom.us
- **When**: Jun 19 2024, 16:00-16:30 UTC
- **Contact**:
- Name: Chris Dickinson
- Email: [e-mail]

## Logistics

The meeting will be on a zoom.us video conference.

## Attendees

- Chris
- Shekar
- Caleb

## Agenda items

- Feedback on [Three possible interfaces for tracing #13](https://github.com/WebAssembly/wasi-observe/pull/13)
- What is the process going forward?

## Minutes

- Feedback
- [caleb] 3 approaches
- 2c: need to support multiple – each has disadvantages
- we can cover disadvantages
- it's loose high level wit right now
- [shekar]: will spend some time on the PR this week
- someone is writing a wasm based app, they can start instrument and have it be exported out
- [caleb]: correct. i think at least at the start we'll have our own libraries; it might be worth
talking about having the otel libraries support wasm directly when compiling to that target
- [shekar]: host provides the network path
- [caleb]: yep. that's a key distinction between the interface types; for span and processor kinds it
it's acting as a provider for the traces; the exporter version is just providing the networking path
- [cd]: high precision timers
- how many folks need to gate access to high-precision timers?
- [caleb]: speaking of, it might be a good time to get feedback from vendors on this
- [cd]: I'll start drumming up attention
- next steps
- [cd]: We could release just tracing and launch other signals later. Steps are feature proposal -> spec text -> implementation -> standardize feature -> accepted. Once we've landed on a tracing wit we probably want to get an implementation or two and then try to write a spec text.
- [shekar]: what is the relation to wasi-logging?
-
- call for feedback on threads

## Action Items

(holding off on these until it's not a holiday)

- [CD]: Get attention on the PR
– ping Ben (and see if he's got any former colleagues at DD that could take a look too)
- ping honeycomb pollinators
- Specifically ask the WASI threading folks for feedback
- [CD]: Reach out to Dan re: wasi-logging in #wasi
- cc Caleb and Shekar
- Goal is to figure out what the state of the proposal is, what kind of work we'd be taking on to pick it up as a dependency
- [CD]: Reach out to Luke/Patrick/Dan – what does phase 2's "spec text available" mean in context of WASI proposals?
- I wasn't able to find spec text for most phase 2 proposals on a cursory look

[shekarbommas]: TKTK
[Danielle]: https://github.com/endocrimes
[JC]: https://github.com/jcchavezs
[CD]: https://github.com/chrisdickinson
[Caleb]: https://github.com/calebschoepp
[Matthew]: https://github.com/f5yacobucci
[Luke]: https://github.com/lukewagner
[Brooks]: https://github.com/brooksmtownsend
[Walther]: https://github.com/walther

# Agenda: May 22 WASI Observe Video call

- **Where**: zoom.us
- **When**: May 22 2024, 16:00-16:30 UTC
- **Contact**:
- Name: Chris Dickinson
- Email: [e-mail]

## Logistics

The meeting will be on a zoom.us video conference.

## Attendees

- Chris

## Agenda items

- [CD]: Poll for updates

## Minutes

- CD: polling for updates

## Action Items

- No action items

[Danielle]: https://github.com/endocrimes
[JC]: https://github.com/jcchavezs
[CD]: https://github.com/chrisdickinson
[Caleb]: https://github.com/calebschoepp
[Matthew]: https://github.com/f5yacobucci
[Luke]: https://github.com/lukewagner
[Brooks]: https://github.com/brooksmtownsend
[Walther]: https://github.com/walther

# Agenda: Apr 10 WASI Observe Video call

- **Where**: zoom.us
- **When**: Apr 10 2024, 16:00-16:30 UTC
- **Contact**:
- Name: Chris Dickinson
- Email: [e-mail]

## Logistics

The meeting will be on a zoom.us video conference.

## Attendees

- Chris
- Walther
- Caleb

## Agenda items

- [CD]: Poll for updates

## Minutes

- CD: polling for updates
- I'm kind of underwater at work, no progress to speak of on wasi-observe
- Caleb, same; kind of underwater
- Walther, same
- CD: calling it for this meeting
- Caleb: any updates on the alternative WIT?
- CD: not yet!
- CD: if anything comes up and we need to meet up, we can confer in the zulip and meet ad-hoc, otherwise, see you all at the next fortnightly!

## Action Items

- No action items

[Danielle]: https://github.com/endocrimes
[JC]: https://github.com/jcchavezs
[CD]: https://github.com/chrisdickinson
[Caleb]: https://github.com/calebschoepp
[Matthew]: https://github.com/f5yacobucci
[Luke]: https://github.com/lukewagner
[Brooks]: https://github.com/brooksmtownsend
[Walther]: https://github.com/walther

---
# Agenda: Mar 27 WASI Observe Video call

- **Where**: zoom.us
- **When**: Mar 27 2024, 16:00-16:30 UTC
- **Contact**:
- Name: Chris Dickinson
- Email: [e-mail]

## Logistics

The meeting will be on a zoom.us video conference.

## Attendees

- Chris
- JC
- Caleb

## Agenda items

- [CD]: Poll for updates
- [CD]: Intent to start a bytecodealliance zulip stream.
- [Caleb]: Wasmcon CFP closing soon, do we want to submit?

## Minutes

- Caleb: earlier this week, started building prototype host component support to see what that would look like in spin. Doing the work of what that looks like in spin
- JC: added a few comments to the PR from Danielle; hoping we could discuss during wasm i/o/kubecon but thigns were busy
- looking at dylibso features and all that; have some reluctance around making the span object first class
- would like to discuss in a broader audience
- approach where everythign is just a function, and you create a span -- imo you don't need to keep an object for the span, you can know everything when you close a span. It can be confusing re: which clock are you using.
- still working on the wasm-tracing library, mainly for a PoC; would love to have more discussion
- thought we agreed to have a backchannel
- Chris: podcast, call for participants
- discussion of how to move forward with the PR
- CD: should we merge? cut PR with additional commits?
- JC: I'm a little worried about accepting a WIT without a reference implementation, given that it'd be easy to take on breaking changes
- Caleb: it might be interesting to see a more function-based WITs as I'm working through a reference implementation
- JC: I can do that – I don't want to move forward without a reference impl

## Action Items

- CD: Create [#wasi-observe](https://bytecodealliance.zulipchat.com/#narrow/stream/431443-wasi-observe) stream in Zulip
- CD: Reach out to Danielle re: the functional WIT

[Danielle]: https://github.com/endocrimes
[JC]: https://github.com/jcchavezs
[CD]: https://github.com/chrisdickinson
[Caleb]: https://github.com/calebschoepp
[Matthew]: https://github.com/f5yacobucci
[Luke]: https://github.com/lukewagner
[Brooks]: https://github.com/brooksmtownsend
[Walther]: https://github.com/walther

---

# Agenda: Feb 28 WASI Observe Video call

- **Where**: zoom.us
- **When**: Feb 28 2024, 16:00-16:30 UTC
- **Contact**:
- Name: Chris Dickinson
- Email: [e-mail]

## Logistics

The meeting will be on a zoom.us video conference.

## Attendees

- Chris Dickinson (moderating, notetaking)
- Danielle
- Caleb
- Matthew
- JC
- Luke
- Brooks
- Walther

## Agenda items

- [CD]: Welcome new members!
- [CD]: Roundtable updates
- [Danielle]: tracing [WIT draft PR](https://github.com/WebAssembly/wasi-observe/pull/12/files)

## Minutes

- [CD]: Welcome new members!
- [CD]: Roundtable updates
- [Danielle]: tracing [WIT draft PR](https://github.com/WebAssembly/wasi-observe/pull/12/files)
- added readback (resources) and flushing (records)
- [JC]: [cd: tktk please correct me] discussion of whether or not we want readback
- [Danielle]: [cd tktk]
- [JC]: Propose moving to issue
- [JC]: set-attribute has a lot of options in otel; strings, booleans, ints, we should think about whether we want to support the full set (or a useful subset)
- [Danielle]: any way to express this in WIT?
- [Luke]: brute-force via multiple methods
- [JC]: support for submitting an event with a timestamp, vs using the host
- [Danielle]: host is your tracing provider, the equiv of your otel provider, which manages timestamps for you
- [JC]: thinking of cases where clients provide you back server time
- [CD]: gesturing at the goal of being a pipe
- [Danielle]: I think most people will use the read-only spans for these purposes
- [CD]: discussion of using the span record to support node-style "oops this span belongs to a different continuation" situations
- [JC]: started working in php a long time ago, supported all frameworks for a long time; but then react-php came out. assumption was that we could access the span because it would be thread-local; when we attempted to instrument, we needed to pass a context
- we explored two things: a context object; passing that as the first arg so you could access the span from the context
- another model: you only store the id
- if you don't have readback, you only need the id – all of the attrs are setters
- you don't need to keep the state, you just keep the id – host holds the state by id

### Action items

---

# wasi-observe 2024 Feb 14

| | |
| -------- | -------- |
| Attending | Chris Dickinson,
| Note Taker |

## Agenda

- [CD] we have new folks here
- welcome luke, matthew
- [CD] General reminder
- Please make sure you're registered with the W3C WebAssembly CG
- Also! Please add yourselves to the champions list on the README!
- [CD] We're in phase 1! What does that mean?
- [CD] Adding context parameter to span/log functions
- https://github.com/WebAssembly/wasi-observe/issues/4
- `wasi-logging` uses a string
- Meeting cadence
- we're meeting fortnightly, is that an okay cadence for folks?