a contact plan could be defined by a script execution reference, eg:
a contactcalc 1.1 2.1 '/tmp/test_evaluator.sh'
where the program receives:
<programName> <fromFqnn> <toFqnn> <from_time_utc> <to_time_utc>
and needs to output eg:
#!cpcalc-begin
2026/03/24-14:22:17 2026/03/24-14:31:44 512000
2026/03/24-15:58:03 2026/03/24-16:09:21 1024000
2026/03/24-17:33:49 2026/03/24-17:41:12 384000
#!cpcalc-end
the script would need to be called by a new daemon on demand / on defined schedule for a defined future interval and adds new contact plan entries of type "calculated". (overrides/removes any present calculated entries on successful script execution / valid output)
This could ease ION contact plan integration.
What do you think?
a contact plan could be defined by a script execution reference, eg:
where the program receives:
and needs to output eg:
the script would need to be called by a new daemon on demand / on defined schedule for a defined future interval and adds new contact plan entries of type "calculated". (overrides/removes any present calculated entries on successful script execution / valid output)
This could ease ION contact plan integration.
What do you think?