Statistics
Following are the list of counters that are generated for scenarios where the stale session cleanup process is initiated.
The following metrics track the counter information:
-
overwritten_index_records_deleted - Captures the total number of records deleted due to overwritten or duplicate unique keys at index
Sample query: overwritten_index_records_deleted
The following labels are defined for this metric:
-
errorCode - The error code in the DB response. Example: 0, 502.
-
sliceName - The name of the logical sliceName. Example: session
-
-
overwritten_index_records_skipped - Captures the total number of records detected as stale, but dropped when the queue is full while processing the records for notify or delete.
Sample query: overwritten_index_records_skipped
The following labels are defined for this metric:
-
action - The action that was supposed to be performed for the stale record. Example: delete, notify.
-
sliceName - The name of the logical sliceName. Example: session
-
The following statistics are supported to handle issues of multiple CDL entries updates when multiple Rx STR or N5 Delete received on PCF within a short gap feature:
Note | The following values apply to all the statistics:
|
-
record_conflict_merge_total - Captures the total count of conflict merge actions.
The following label is defined for this metric:
-
action
The "action" label supports the following values:
-
ok: Captures success processing of conflict notification.
-
submit: Captures the number of messages submitted to the engine when conflict notification is received from CDL.
-
retry: Captures the number of retry operations occurred during conflict merge.
-
skip_<reason for skip>: Indicates that the PCF is expecting some data validation before the records are merged when CDL notification is received. If that data is missing, PCF logs these skip counters with reason to skip the data.
Reasons to skip the data are:
-
throttle: Due to throttle check.
-
feature_disabled: Feature is disabled.
-
no_geositename: GeoSiteName is not configured.
-
flag1_mismatch: Mismatch of CDL flag 1 at both sites.
-
unsupported_record: Invalid data records of CDL notification.
-
retry_unsupported_record: Invalid data records available during retry.
-
unsupported_lastaction: Invalid lastAction objects are available in notification records.
-
retry_ unsupported_lastaction: During retry lastAction objects are invalid.
-
no_sessionid - Session id is not available in remoteLastAction object.
-
retry_no_sessionid: Session id is not available in remoteLastActoin object.
-
no_remotesessionid: Remote session id is not available to remove in local record object.
-
retry_no_remotesessionid: Remote session id not available to remove in local record object during retry.
-
attemptsdone: Total number of attempts completed.
-
-
error_<cause of error>: Indicates while merging the records some error/exception occurred in that case pcf logs this error related counter.
Following are the types of cause of errors:
-
deletesession: Remote rx session delete operation from the local record failed.
-
retry_deletesession: During retry remote rx session delete operation from the local record failed.
-
removeflags: after deleting remote rx session from local record while removing corresponding flags from local record failed.
-
addactionlist: Failed to consolidated all action list objects from local and remote records.
-
nopk: Primary key is not available in the record.
-
retry_nopk: Primary key is not available in the record during retry.
-
For information on statistics, see Ultra Cloud Core Common Data Layer Configuration and Administration Guide.