i18n_token is deleted when you modify alarm message
Article ID: 130643
Updated On:
Products
DX Unified Infrastructure Management (Nimsoft / UIM)
Issue/Introduction
The value of "i18n_token" is deleted when modifying alarm message through Message Pool Manager.
Environment
Any probe
Cause
This is a design.
If "Activate support for internationalization" is turned on in nas probe,
UMP uses "i18n_token" to translate alarm message.
This is translation resource file that UMP uses.
<Nimsoft>\probes\service\wasp\i18n\Nimsoft_<locale ID>.properties
If you modify original alarm message in probe side, UMP do not know the change.
To prevent inconsistency from happening, probe will remove "i18n_token" for alarm message that have been modified.
If "Activate support for internationalization" is turned on in nas probe,
UMP uses "i18n_token" to translate alarm message.
This is translation resource file that UMP uses.
<Nimsoft>\probes\service\wasp\i18n\Nimsoft_<locale ID>.properties
If you modify original alarm message in probe side, UMP do not know the change.
To prevent inconsistency from happening, probe will remove "i18n_token" for alarm message that have been modified.
Resolution
No resolution for this behavior.
Additional Information
Not all monitoring probes have "i18n_token" for alarm message. (for example, logmon alarm does not have "i18n_token")
For alarm message which does not have "i18n_token", UMP uses original alarm message for display.
For alarm message which does not have "i18n_token", UMP uses original alarm message for display.
Feedback
Yes
No
Powered by
