When importing a modified rule, the rule action is not being imported.
Following use case:
A set of rules are being exported into a XML file. Then the needed modification is being done in this file. All components can be modified: conditions, thresholds, scopes, action, ... Finally the modified XML file will be imported into all Foglight Management Server in the environment.
All modifications will be imported, except the action. The action stays the same and is not being changed
To enable XML file import or cartridge upgrade follow the steps below:
Why is the action left untouched?
The actions are typically used to report alarms and such to external entities - there are environments, where a rule action fires off a perl script, which in turn copies the alarm into an external Siebel database or something similar. More typically someone will simply modify the existing email action to report something sensible or delete it entirely.
Those setups have "only" modified the action to better suit the environment's reporting needs. When upgrading such environments, it would suck to overwrite the modifications with the contents of upgraded cartridges.
This use case and the use case described above are polar opposite. The Foglight design is following the upgrade from one version to another. In this case, the feature is being used to modify and roll out rules. It is impossible to fix one without breaking the other.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center