-
Titel
End User: Changing the storage format of an existing custom field may cause errors in the Archiver when capturing new data as well as querying for existing data. -
Beschreibung
ISSUE:
Recived the alert End User: Archiver Data Storage FailureRule End User: Archiver Data Storage Failure fired with severity level Warning. Archiver was unable to write some buffers to its MySQL database. Some Hit data has been lost. This alarm may indicate system is overloaded
-
Ursache
CAUSE:
One cause for this issue could be that the storage format type of an existing custom field was changed
Changing the storage format of an existing custom field may cause errors in the Archiver when capturing new data as well as querying for existing data.
The errors which occur during capture result in loss of data.
Once a custom field is created, its storage format should not be changed. If they want to change the storage format, they can delete the custom field and create a new custom field. The name of the custom field may be reused since its tracked internally by its uuid.
-
Lösung
RESOLUTION:
APMDATA-2047 was created as an enhancement to make it impossible to change the storage format type of an existing custom field
-
Fehler-ID
APMDATA-2047