MACRO::JSON_OUTPUT_A(3stap)

💖 MACRO::JSON_OUTPUT_A(3stap) — the JSON Tapset one, bestie 💖

okay so you found the MACRO::JSON_OUTPUT_A(3stap) page and honestly? good instinct. this is the SystemTap JSON tapset corner of the manual and it's lowkey iconic. let's get into it 🦋

---

✨ NAME ✨

macro::json_output_array_numeric_value — spits out a numeric value for a metric that lives inside an array. that's the whole job. she's focused, she's employed, she ate 💅

---

🌸 SYNOPSIS 🌸

@json_output_array_numeric_value(array_name,array_index,metric_name,value)

that's it, that's the call. four things go in, the numeric value comes out. periodt 💖

---

🎀 ARGUMENTS 🎀

• array_name — the name of the array. like, which array are we talking about, bestie. that one. 👑
• array_index — the array index, and it's a string (yes, a string, not a number, don't come for me) that tells it where to store the numeric value. it's giving "coordinates of the vibe". 🗺️
• metric_name — the name of the numeric metric. the ✨name✨ of it. 💜
• value — the actual numeric value you wanna output. the payload. the main character. 🔥

---

💅 DESCRIPTION 💅

okay so the json_output_array_numeric_value macro is designed to be called from the 'json_data' probe inside your script. that's its whole situation. it's not out here doing freelance work — it goes in the 'json_data' probe, no cap.

what it does once it's there: it outputs a metric's numeric value that's sitting in an array. that's the task. 🫶

and important, bestie — this metric should have been added with json_add_array_numeric_metric first. like, you can't just show up with a metric that nobody registered. the add has to happen before the output. that's the order of operations, that's the lore. 📋✨

---

🔍 SEE ALSO 🔍

• tapset::json(3stap) — go read this one too, fr fr, it's the whole friend group 💖

---

and that's the page!! go forth and output your numeric array metrics responsibly, bestie 🦋🌸💅

this was the SystemTap Tapset Reference, Version Ver, dated September 2026 — mwah, take care of her 💜✨