CK Telemetry Report (Legacy Wrapper)

If a workflow you downloaded is demanding a node called CKDispatchReport, you don't need to hunt down some dead pack. It ships in ComfyUI-CK-Telemetry, it still works, and its display name is honest about what it is: CK Telemetry Report (Legacy Wrapper).

It's the same telemetry engine as the pack's main node. Same comfy_kitchen registry instrumentation, same 500 ms resource sampling, same six widgets, same report. The difference is the socket shape, and it's the older, wildcard one.

What's different about it

The class declares an optional input of type * (the tooltip literally says "Legacy fallback passthrough") and hands it straight back out of an output of the same wildcard type. Alongside that it exposes report as a STRING - the same text you'd read in the node's field, available as a wire you can send to Preview as Text. So it's a pass-through node that happens to write a diagnostic report, which means you can slot it into a working graph almost anywhere, including downstream of a Save node, without breaking the data flow.

Two structural details worth knowing, because they change behavior:

• It's flagged is_deprecated in the schema. That's a compatibility marker, not a broken-node marker - ComfyUI keeps loading it so early development workflows don't explode. New graphs should use CK-Telemetry instead; the engine is identical and the main node is the maintained one.
• It's an output node, so it executes even if nothing consumes its output. In practice that's a feature: you can park it at the end of a graph and treat it as "collect the report for this run" without wiring it to anything.

The settings

The widget set is the pack's shared one, and the defaults are the loud ones - show_terminal_report on with a summary terminal report, and node_report_level on detailed. That's roughly what you want from a node you added on purpose.

• terminal_report_level - summary or detailed, governs the terminal dump when show_terminal_report is on.
• node_report_level - summary or detailed, governs the field, the report output and the embedded metadata together.
• embed_metadata - writes the structured report and the text report into EXTRA_PNGINFO, so a downstream native saver writes them into the file, and the pack's frontend extension refills the node's report field when that file is dropped back onto the canvas.
• show_node_report - collapses the read-only report_text field, which is handy on cramped canvases. report_text is the display, not something you wire.

The elapsed number on the report is time measured up to this node. Put it after your sampler and VAE decode and you're timing most of the workflow; put it right after the sampler and you're timing the sampler stage. Both are legitimate, they're just different questions.

Install

Manager, search CK-Telemetry (the pack title, not the node name), or:

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

Restart ComfyUI. The only real dependency is psutil>=5.9.0, and the pack targets recent ComfyUI builds - it's written against the V3 node API, so a very old install won't register any of these nodes.

Troubleshooting

Can't find it in the node search. The palette labels deprecated nodes differently, so type the class name exactly (CKDispatchReport) or one of the pack's aliases (legacy ck telemetry) rather than relying on fuzzy matching.

Report says "No Comfy Kitchen backend selections observed." Nothing went through the comfy_kitchen registry during that prompt - usually an older ComfyUI without it. Verify from ComfyUI's own Python environment:

python -c "import comfy_kitchen as ck; print(ck.registry.list_backends())"

Report field is blank after a run. The node didn't execute. If it's bypassed, or the workflow ends on a branch that never reaches it, nothing gets written - you'll also get no terminal report.

Report only appears in the terminal, never in the PNG. Check embed_metadata is on, and check you aren't launching with --disable-metadata, which stops ComfyUI writing prompt metadata into files at all.

And if you're starting from scratch today, reach for CK-Telemetry. There's no reason to build new graphs on the legacy wrapper.