TORRUS_SRVDERIVE(8)

📦
version 3.00 · 3 versions
, in debian bookworm, debian trixie, ubuntu noble, ubuntu questing

💖 TORRUS_SRVDERIVE(8) 💖

okay bestie, welcome to TORRUS_SRVDERIVE(8) from the torrus manual set — this is the page for the srvderive command and it's literally the girlboss of combining service data. sit down, grab a boba, we're doing math on purpose 🧮✨

✨ NAME ✨

srvderive — derive a whole new service ID from the sum or maximum of other service values. it's giving "found family of metrics" 💅

🌸 SYNOPSIS 🌸

torrus srvderive TIMESPAN OUTPUT FUNCTION SOURCES...

that's the whole vibe check right there. four little pieces and you're done 🦋

🎀 DESCRIPTION 🎀

so when the Torrus Reporting engine is all set up, this command is the one that takes several services' data and squishes them together into one brand new service ID. the output data is either the maximum or the sum of the input services. no cap, that's it.

if you want the whole story, go read the Torrus Reporting Setup Guide. it has the lore 📖

⏰ TIMESPAN ⏰

heads up bestie: either the --month option or the --end option must be defined. pick one, you can't skip this part 🙈

  • --start=YYYY-MM-DD — sets the start date of the calculation. this is where the counting begins 💖
  • --end=YYYY-MM-DD — sets the next day after the end of the period. yes, the next day. it's the day after the end, keep that in mind 👀
  • --month — instead of manually setting the end date, just use this and it's so convenient honestly. it sets the end date to one calendar month after the start date. one month, done, slay 🌙

📤 OUTPUT 📤

  • --out=SERVICEID — sets the output service ID. this should not be a service ID that's used in the Torrus datasource trees, okay?
⚠️ note: if you run srvderive twice with the same arguments, the produced data gets doubled for the output service ID. not a vibe. don't do that. 💀

🧮 FUNCTION 🧮

  • --func="MAX"|"SUM" — sets which function gets used when combining the input service data. currently only "MAX" and "SUM" are supported. that's the whole menu, bestie, and honestly both of them ate 🔥

📥 SOURCES 📥

  • --in=SERVICEID ... — input service IDs get specified either with the --in option, or as plain command line arguments. either way works 💅
🫶 at least 2 input service IDs should be specified. one is not a party, it's just a lonely little metric.

👑 OPTIONS 👑

  • --step — default: 300. sets the data interval for the derived service ID. it's recommended to leave this option at the default value. don't touch it, she's fine, she's thriving 🌸
  • --verbose — prints extra information. yapper mode: on 🗣️
  • --debug — prints debugging information. for when you need to know everything 🔍
  • --help — prints command usage information. your friendly lil tour guide 🧚

🦋 SEE ALSO 🦋

📝 NOTES 📝

more documentation lives at the Torrus home page: http://torrus.org — go peruse, iykyk 🌈

💜 AUTHOR 💜

Stanislav Sinyagin <ssinyagin@k-open.com> — thank you for your service, king 👑

and that's the page!! this was torrus 3.00, dated 2023-05-02, page TORRUS_SRVDERIVE(8). mwah, periodt 💋✨🎀

📦 where this page comes from