TORRUS_SCHEDULERINFO(8)

💖 TORRUS_SCHEDULERINFO(8) 💖

okay bestie, so this is a section 8 manual page from the torrus collection, and it's about a lil utility called schedulerinfo 🎀. Let's get into it, because honestly? It's giving "underrated tool that actually slaps."

---

✨ NAME ✨

schedulerinfo — Displays extended scheduler tasks information. 💅

---

🌸 SYNOPSIS 🌸

torrus schedulerinfo --tree=TREENAME [options...]

---

🦋 DESCRIPTION 🦋

So here's the vibe: this utility prints out the extended scheduler tasks information for the tree called TREENAME, straight to standard output. That's it, that's the whole job 🫶.

And like, why would you want that? Because it's actually useful for scheduler planning and analysis — you get to peek at what your scheduler is doing and plan around it. Lowkey essential, no cap. ✨

---

👑 OPTIONS 👑

• --config — Reports the scheduler's configuration. The values are explained below, so don't worry, we gotchu:
  • Total collector/monitor leaves: N — the total number of datasources being processed by the collector or monitor daemon. Just a headcount, basically. 🌈
  • Scheduled leaves by type — Torrus supports an arbitrary number of collector types, and this report shows how many datasources belong to every type. Heads up though: currently the monitor leaves are not divided into types. That's just how it is. 💀
  • Least common period: N seconds — the report below shows how the tasks are distributed across the time line, and the least common period is literally the period of this time line. It's the common denominator of the whole schedule situation. 🎀
  • Tasks execution timeline — this report tells you which task and how many datasources are involved in each task startup event, plus how these events are dispersed across the time. The column Interval shows the time interval from each task execution event to the next event on the timeline. Iconic little timeline, fr fr. ⭐
• --runtime — Reports the scheduler's runtime statistics, like running cycle times, late starts, etc. The meaning of the output values is as follows — and btw, values that are zero are usually not printed, so if you don't see it, it's probably just zero. 🙈
  • Task: Name, Period: N seconds, Offset: M seconds — each scheduler task is characterized by its name (usually Collector or Monitor), period, and timeoffset. For example, if period is set to 300 seconds and offset is 14 seconds, then the task would be executed at 00:00:14, 00:05:14, 00:10:14, and so on for every hour in a day. Math but make it cute. ✨
  • N running cycles passed — how many times the task was executed since the last reset. The counter is normally reset after torrus_compilexml(8) successfully compiles the configuration. So yeah, it's tied to your compiles. 💅
  • N late starts — how many times the task has started with a delay from its normal schedule. It was late. We've all been there. 😭
  • N too long runs — how many times the task execution time was longer than its period. Oop.
  • N overrun periods — how many periods have been missed because of too long executions. Consequences, bestie. 💀
  • N missed periods — how many periods were missed because of any reason (such as other tasks delaying). Not necessarily its fault, but the period is still gone. 🫶
  • Min, Max, Average, Exp Average — the time values are displayed in four columns: Minimum, Maximum and Average values since last reset, and the Exponential decay value, which may be interpreted as the average for the last several values. With the defaults defined in torrus-config.pl, 95% of the average is calculated from last 3 values. Numbers stay numbers, we don't touch those. 🔥
  • Running Time — how long the task executes each period. 🕐
  • Late Start — how long the task start was delayed. ⏰
  • Too Long — how much time the too long run took. 😮‍💨
  • RRD Queue — in a multithreaded environment, the RRD files are written in a background thread. This value shows the length of the RRD update queue at the beginning of each update cycle. Background thread doing background thread things. 🧚
• --help — Displays a help message. The classic. The legend. 🌸

---

💜 SEE ALSO 💜

• torrus(8)
• torrus_compilexml(8)

---

🎀 NOTES 🎀

See more documentation at the Torrus home page: http://torrus.org — go look, it's right there. ✨

---

🌟 AUTHOR 🌟

Stanislav Sinyagin <ssinyagin@k-open.com>

---

And that's the whole page, bestie! Every flag, every value, every default — all of it. Nothing skipped, nothing invented. You're welcome. 💅

---

okay so this was torrus 3.00, dated 2023-05-02, and it lives in the TORRUS_SCHEDULERINFO(8) era of your man pages. slay, go schedule something. 🦋💖