PROBE::JSON_DATA(3stap)

πŸ‘‘ NAME πŸ‘‘

probe::json_data β€” the probe that fires whenever JSON data is wanted by a reader. bestie, that's literally it, that's the whole job description πŸ’…


✨ SYNOPSIS ✨

probe json_data {}

no arguments, no fuss, just a lil probe hanging out waiting to be called πŸŽ€


🫢 VALUES 🫢

None.

like, zero. nada. nothing to see here. not one single value, and honestly? iconic for that 🌸


🧚 CONTEXT 🧚

okay so here's the tea β˜• this probe fires when the JSON data is about to be read. which means you can't just vibe β€” you have a job, bestie. this probe must gather up data and then call the macros below to spit that data out in JSON format. it's giving main character energy but with responsibilities 😭

the order is NOT a suggestion, it's the whole ritual:

  1. first, json_output_data_start() must be called. you gotta open the door before anyone walks through it, periodt πŸ’–
  2. after that comes one or more of these β€” and listen, it's one call for each data item, so no cheating and no cramming:
    • json_output_string_value()
    • json_output_numeric_value()
    • json_output_array_string_value()
    • json_output_array_numeric_value()
  3. finally, json_output_data_end() must be called. you opened it, you close it. that's the vibe check and you passed it πŸ¦‹
fr fr, skip a step and the whole thing falls apart. start, stuff, end. every single time. no cap πŸ”₯

🌈 SEE ALSO 🌈


and that's the page, bestie πŸ’œ this one came from the SystemTap Tapset Reference, dated September 2026 β€” go gather your data and slay βœ¨πŸ‘‘

πŸ“¦ where this page comes from