This section has information to help identify and resolve system issues.
THE MATRIXX RERATING SOFTWARE PROGRAM IS EXPERIMENTAL AND IS NOT AUTHORIZED FOR PRODUCTION USE. IT IS PROVIDED “AS-IS” WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED.
Use MATRIXX Rerating to reprocess messages for a range of dates previously processed by the Charging Server that were determined to have incorrect results due to errors in the pricing or tax configuration, or when a subscription was incorrectly provisioned, after the issue is resolved. MATRIXX Rerating supports past billing cycle periods for postpaid subscriptions.
A deployment of the MATRIXX Rerating components consists of containers installed with a Helm chart in a multi-node Kubernetes cluster.
rerating/c_rerating_administering.html#concept_x5d_qbv_lwb__fig_hck_cxz_5wb illustrates the MATRIXX Rerating components and process.
Use this section to understand events delivered to the billing system when a job is approved by the operator in Rerating Workbench, and transaction events which are generated by the live system when messages are rerated.
An operator manges rerating through the Rerating Workbench user interface.
Apache HBase has the following dependency:
Run probe through Helm chart configuration.
In HBase, if no checkpoint and no changes are found for a subscriber, use the following steps to find changes.
To resolve the FAILED_PRECONDITION: COULD NOT MODIFY SCHEMA error, for example:
Use the following sideloader values to unpack the contents of sideloader images into /opt/mtx/conf.
Use the following steps to resolve error code 8192.
If the Rerating Director is not polling a job while Rerating Workbench is showing job status as PENDING_PREV_JOB, check if the previous job ran into an error. This is a Rerating Orchestrator issue. To work around this error, abort and delete the previous job.
Event Streaming Framework 1 (ESF1) throws a NullPointerException exception if the rerating flag is not enabled.
Event Streaming Framework 1 (ESF1) can break with nullptr exception on missing values. For example:
Event Streaming Framework 1 (ESF1) and Event Streaming Framework 2 (ESF2) can throw the following error due to a schema mismatch:
If Event Streaming Framework 2 (ESF2) throws the following error:
If primary events are not processing on Event Streaming Framework 3 (ESF3), first grep for PrimaryEvents in esf3.log.
