sflow feature map
Find your path through sflow
Start with your job—not a documentation hierarchy. Follow a need to the right feature, open the exact guide, and pick up practical tips along the way.
How to use this map
1. Choose a common need below, or select a map goal.
2. Follow the branch to the smallest feature that expresses your intent.
3. Hover for a "Use when..." hint; click to open the exact docs.
4. Search across every feature when you already know a keyword.
Tip: validate with --dry-run before spending cluster time.
Common starting points
What do you need right now?
Each shortcut opens the matching branch of the map. From there, choose a feature to open its documentation.
Recommended learning path
- Run the Quickstart once.
- Adapt a runnable sample workflow.
- Keep the Quick Reference open while editing YAML.
Useful habits
- Run
--dry-runbefore a real allocation. - Add readiness probes to long-running servers.
- Use failure
log_watchprobes for tracebacks. - Use named artifacts instead of inline shell heredocs.
When a run fails
- Start with
sflow_summary.log. - Open the failing task's
task.logand command log. - Compare timestamps with hardware monitoring.
- Use the error-analysis skill for guided triage.