Home
MATRIXX Event Streaming
Administering Event Streaming
The Event Stream Server and Event Streaming Framework require administration tasks. The Event Streaming Framework administration tasks includes manually recovering events from streamed event files.
Manually Recovering Events from Streamed Event Files
Use the create_event_files_from_txn_logs.py script to manually recover events from a _glossary/streamed_event_file.html. This script creates an output file containing events from a given _glossary/global_transaction_counter.html range for SEFs.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
- About MATRIXX Event Streaming
  MATRIXX Event Streaming describes the tasks required to create custom event streams for events received by your MATRIXX environment. An event stream is sent to the Event Streaming Framework from the Event Stream Server running on MATRIXX Engine. The Event Stream Server provides the APIs, libraries, and other files needed to create custom event streams. The Event Streaming Framework provides connectors for sending event stream data to event stream platforms, such as Kafka and ActiveMQ.
- Event Streaming Overview
  Use event streaming to integrate downstream message systems with MATRIXX. Fully optimize these message systems to filter, transform, and deliver events to multiple secondary targets.
- Implementing Event Streaming
  Use these steps as a summary of tasks required for event streaming in a MATRIXX environment.
- Event Streaming Framework Connectors
  An Event Streaming Framework connector is required to stream events. Out-of-the-box connectors are explained in this section. For information about setting the log level for individual connectors, see the discussion about monitoring event streaming in MATRIXX Monitoring and Logging.
- Administering Event Streaming
  The Event Stream Server and Event Streaming Framework require administration tasks. The Event Streaming Framework administration tasks includes manually recovering events from streamed event files.
  - Manually Recovering Events from Streamed Event Files
    Use the create_event_files_from_txn_logs.py script to manually recover events from a _glossary/streamed_event_file.html. This script creates an output file containing events from a given _glossary/global_transaction_counter.html range for SEFs.
  - Monitor Event Streaming
    To monitor and troubleshoot event streaming, you can create a custom Grafana dashboard or collect statistics from Prometheus.
  - Configure Event Restreaming for Failed Events
    Perform this task to restream failed events.
  - Reset Event Streaming and Reprocessing Events
    Resetting event streaming in a cloud native environment involves resetting the Event Streaming Framework (ESF) cursor after the ESF and MATRIXX Engine are redeployed.
  - Reprocess Failed Events
    Events are failed if they cannot be published to the event consumer. You must configure a failed_delivery_rate parameter in each connector that you want to collect failed events for. This parameter sets an event failure rate percentage. If failed events exceed that rate, they are reprocessed or collected in a file for later inspection and possible reprocessing. This task explains how to manually reprocess failed events.
  - Troubleshooting
    To troubleshoot and recover from an event streaming failure in a cloud native environment, you can refer to the provided Grafana dashboard.
- Appendixes
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Manually Recovering Events from Streamed Event Files

Use the create_event_files_from_txn_logs.py script to manually recover events from a Streamed Event File (SEF). This script creates an output file containing events from a given Global Transaction Counter (GTC) range for SEFs.

By default, files are saved to the current directory. The file output location is configurable.

You use this script to recover events after receiving error messages that call for manual recoveries, like these:

LM_ERROR 12565|4110 2020-02-06 21:52:41.463720 [event_stream_server_2:2:1:1(5200.72299)] | 
EventStreamReader::EventStreamReader::loadGtcsFromFile: Detected missing GTCs: 148256176 ... 
148256176. Manual recovery is required.
LM_ERROR 12565|4110 2020-02-06 21:52:42.978290 [event_stream_server_2:2:1:1(5200.72299)] | 
EventStreamReader::EventStreamReader::loadGtcsFromFile: Detected missing GTCs: 148256176 ... 
148256176. Manual recovery is required

To recover events manually from the Event Streaming Framework:

Record the lowest GTC in the first error message.
Record the lowest GTC from the next (good) SEF file.
Run create_event_files_from_txn_logs.py while using the two GTCs you recorded as the StartingGTC and EndingGTC. You must manually create the output directory.
For more information, see the discussion about create_event_files_from_txn_logs.py.
Fail over the standby publishing pod.

Note: Events are recovered from SEF files in MATRIXX Event File (MEF) streaming environments. If the automatic recovery of events is disabled or fails for any reason, you can still use the manual recovery process.