Comfy Kitchen Dispatch Report (Legacy Image)

This is the image-shaped version of the CK-Telemetry report node, and the shape is the whole point. Where the pack's main node takes a wildcard * and will happily sit anywhere, this one demands an IMAGE on its way in and gives you an IMAGE back out. Its display name says the rest: Comfy Kitchen Dispatch Report (Legacy Image) - it exists so older workflows keep loading, and it is flagged deprecated for that reason.

Why the typed socket is actually useful

A wildcard socket accepts anything, which means a wildcard pass-through can be wired into a latent by mistake and will simply carry it along without complaining. An IMAGE socket is type-checked by ComfyUI: it takes an image and will refuse anything else. If what you're documenting is "this picture came out of this pipeline," that guarantee is worth more than flexibility - the telemetry node can't silently end up somewhere you didn't intend.

It's also the honest way to attach a report to an image you're publishing. With embed_metadata on, the report goes into EXTRA_PNGINFO under comfy_kitchen_dispatch and comfy_kitchen_dispatch_report, and the next native saver in the chain writes it into the file alongside the workflow itself. So the PNG carries the numbers - which kernel dispatched, how many selections, what the CPU and VRAM were doing - and dropping that file back onto the canvas refills the node's report field. The output report (STRING) is the same text as a wire, for Preview as Text.

Inputs and outputs

• image (required, IMAGE) → image (IMAGE pass-through, untouched).
• report (STRING) - the diagnostic text.
• The pack's shared controls: terminal_report_level and show_terminal_report for the terminal dump, node_report_level for how deep the field/output/metadata get, embed_metadata, plus show_node_report to collapse the read-only report_text field. Peak/average resource numbers come from a 500 ms sampler thread; elapsed time is measured up to this node, so put it where the question you're asking ends.

One structural note: this node is not an output node. It doesn't force itself to run like the pack's wildcard report node does. It executes because something downstream needs its image output - so keep it in the live branch feeding your Save node, not parked on a dead-end wire.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/Elsewhere101/ComfyUI-CK-Telemetry

Or install ComfyUI-CK-Telemetry from ComfyUI Manager by searching CK-Telemetry. Dependencies are effectively one package (psutil>=5.9.0), and the pack needs a current ComfyUI since it's written against the V3 node API.

Troubleshooting

Report field stays empty. The node didn't run. Since it isn't an output node, a disconnected image output or a bypassed node means no execution, no report, no metadata.

Report exists but no PNG metadata. Confirm a native save node is downstream of the image output - the report rides in EXTRA_PNGINFO, which only a saver writes to disk - and confirm you aren't launching ComfyUI with --disable-metadata, which turns off prompt metadata in files entirely.

Elapsed time looks suspiciously small. That's the "up to this node" measurement biting you. If you want the full workflow timed, this node has to be after decode and save, not right behind the sampler.

For new workflows, use CK-Telemetry - same engine, wildcard passthrough, and it's the node the author is actually maintaining.