-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major
-
None
-
Affects Version/s: master
-
Component/s: Monitord
-
None
Monitord supports many command-line arguments, but currently there isn't a good way to specify them at a workflow level.
We should add a feature to allow users to specify monitord arguments using a property that get propagated to monitord at runtime. Alternatively we could use environment variables, or a transformation catalog entry. The exact mechanism is TBD.
- duplicates
-
PM-948 support for pegasus.monitord.arguments
- Closed