Monitoring

Live Monitoring in iTextPRO

The Live Monitoring module in iTextPRO is designed to dynamically track and analyze key data points related to SMS traffic. It offers real-time insights into traffic congestion, load, delivery, and more, empowering users to make critical routing decisions on the fly.

1. User Benefits:
Proactive Traffic Management:
Users can proactively manage SMS traffic based on live monitoring data.

2. Optimized Routing:
Dynamic insights support optimized routing decisions for improved delivery.

3. Efficient Resource Allocation:
Helps allocate resources efficiently during peak business hours.

4. Enhanced Performance:
Live monitoring contributes to enhanced system performance and responsiveness.

In summary, the Live Monitoring module in iTextPRO ensures that users have access to up-to-the-minute insights, enabling them to navigate and optimize SMS traffic effectively, especially during peak business hours.

PDU Logs

iTextPRO employs a robust PDU (Protocol Data Unit) logger to capture and log every message entering or leaving the SMSC. This valuable tool facilitates troubleshooting and provides essential data for monitoring and maintenance. Key features of iTextPRO's online PDU logger include:

1. Real-time Message Journey:
Captures and logs each message in real-time.
Facilitates immediate troubleshooting and analysis.

2. Filtering Capabilities:
Equipped with a filter to trace the journey of any message with a single click.
Allows users to inspect various PDU types such as SubmitSM, DeliverSM, Bind, Unbind, etc.

3. Visibility and Time Frame:
Logs are visible in the admin time zone, ensuring accurate timestamp references.
By default, logs are retained for 3 days, providing a relevant timeframe for troubleshooting.

4. Upstream Traffic Inspection:
Logs Upstream traffic, allowing users to check the SMS journey.
Users can select the gateway from the configured drop-down list to inspect Upstream traffic.

5. Troubleshooting Support:
Facilitates efficient troubleshooting by offering real-time visibility.
Essential for diagnosing issues related to message delivery and SMPP interactions.

Usage Guidelines:
Users can access the PDU logger through the iTextPRO interface.
Utilize the filter to focus on specific messages and inspect their journeys.
Upstream traffic logs help in verifying the SMS journey and identifying any issues.
Regular monitoring of PDU logs aids in maintaining a robust and reliable SMS system.

The 3-day default visibility period strikes a balance between retaining relevant data and managing storage resources.

 
iTextPRO Verbosity Levels in PDU Logging:

iTextPRO's PDU logging system offers different verbosity levels to provide detailed insights into the communication between the application and the SMPP gateway. Here's an overview of the key verbosity levels:

1. Bind Request:
Purpose: Initiates the process of binding the SMPP gateway.
Action: iTextPRO sends a connection request to establish an SMPP connection.

2. Bind Response:
Purpose: Indicates the SMPP gateway's response to the connection request.
Action: The response from the SMPP gateway to iTextPRO is referred to as "BIND RESPONSE."

3. Enquire Link Request/Enquire Link Response:
Purpose: Conducts a health check to ensure the SMPP gateway session is alive and connected.
Action: iTextPRO sends an Enquire Link Request, and the SMPP gateway responds with an Enquire Link Response.
Note: The recommended interval for this check is 30 seconds.

4. Submit_SM Request:
Purpose: Initiates a message request from iTextPRO to the SMPP gateway.
Action: iTextPRO sends a request for message submission.

5. Submit_SM Response:
Purpose: Represents the message response received from the SMPP gateway against the submitted message request.
Action: The SMPP gateway responds to iTextPRO's message submission request.

6. Deliver_SM Request:
Purpose: Indicates the Delivery Report (DLR) received by iTextPRO for a message submitted to the SMPP gateway.
Action: The SMPP gateway sends a request related to the delivery status of a submitted message.

7. Deliver_SM Response:
Purpose: Acknowledges the Delivery Report (DLR) request received by iTextPRO.
Action: iTextPRO acknowledges the DLR request in the Deliver_SM Response.

8. Unbind_Request:
Purpose: Initiates the Unbind request to terminate connected sessions between iTextPRO and the SMPP gateway.
Action: iTextPRO or the SMPP gateway sends the Unbind request.
These verbosity levels in PDU logging are essential for monitoring and troubleshooting, providing administrators with a detailed view of the communication flow between iTextPRO and the SMPP gateway. The information captured at each level contributes to maintaining a reliable and efficient SMS system.

Event Viewer Client:
The iTextPRO Event Viewer (Client) monitors and logs system events, providing administrators with a detailed view of errors and crashes impacting SMS traffic. This tool aids in proactive issue resolution and efficient troubleshooting, ensuring system stability.

Key Features:
Monitors iTextPRO events.
Presents detailed error log information.
Facilitates proactive troubleshooting.
Logs visible in admin time zone.

Benefits:
Proactive issue resolution.
Enhanced troubleshooting.
Maintains system stability.
 
Note: Regularly checking the Event Viewer is crucial for staying informed and ensuring optimal SMS platform performance.

Event Viewer DLR: 

The iTextPRO Event Viewer (DLR) provides insights into errors encountered during Delivery Report (DLR) updates in the iTextPRO system. It captures comprehensive event details, aiding in efficient troubleshooting for seamless problem resolution.

Key Features:
Monitors DLR update events.
Captures detailed error information.
Facilitates effective troubleshooting.
Logs visible in admin time zone.

Benefits:
Swift identification of DLR-related issues.
Streamlined troubleshooting process.
Ensures robust DLR update functionality.

Note: Regularly reviewing the Event Viewer (DLR) is essential for maintaining the reliability of DLR updates and addressing any issues promptly.

Server PDU Logs: 

iTextPRO's SMPP Server PDU Logs are integral for monitoring and troubleshooting message transactions between the ESME (External Short Message Entity) user and iTextPRO. These logs capture downstream traffic, providing valuable insights for efficient issue resolution.

Key Features:
Logs every message transaction.
Essential for troubleshooting.
Logs visible in the admin time zone.

Downstream Traffic:
Tracks the journey of messages from ESME to iTextPRO.

Verbosity Levels:
Offers detailed logs for various transaction types.

Note: Regularly reviewing SMPP Server PDU Logs ensures robust monitoring and aids in swiftly addressing any transaction-related issues for optimal system performance.

iTextPRO's SMPP Server PDU Logs provide detailed insights into message transactions between the ESME user and the platform. Understanding the verbosity levels enhances troubleshooting and system monitoring.

1. Bind Request:
Description: ESME user initiates connection.
Purpose: Establishing connection with iTextPRO.

2. Bind Response:
Description: iTextPRO responds to connection request.
Purpose: Acknowledging ESME user's connection.

3. Enquire Link Request/Response:
Description: Health check call from ESME user.
Purpose: Verifying iTextPRO session status.
Note: Recommended value for check interval is 30 seconds.

4. Submit_SM Request:
Description: ESME user initiates message request.
Purpose: Sending SMS messages to iTextPRO.

5. Submit_SM Response:
Description: iTextPRO responds to message request.
Purpose: Acknowledging SMS message submission.

6. Deliver_SM Request:
Description: DLR received by iTextPRO for submitted message.
Purpose: Updating delivery status for submitted SMS.

7. Deliver_SM Response:
Description: ESME user acknowledges DLR request.
Purpose: Confirming receipt of delivery status.

8. Unbind Request:
Description: ESME user initiates unbind request.
Purpose: Terminating connected sessions.

Note: Regular monitoring of these logs ensures effective communication between ESME users and iTextPRO, facilitating prompt issue resolution.

 Event Viewer Server:

The Event Viewer (Server) option in iTextPRO enables real-time monitoring of application events related to ESME Users. It captures error and crash events affecting customers, providing a comprehensive display of full error logs for effective troubleshooting.

Key Features:
Error and Crash Event Monitoring:
Captures events impacting ESME Users.
Displays comprehensive error and crash logs.

Real-time Monitoring:
Provides real-time visibility into application events.
Enables prompt identification and response to issues.

Troubleshooting Support:
Facilitates effective troubleshooting of problems.
Offers detailed insights for issue resolution.

Note: Event logs are visible in the admin time zone, ensuring accurate tracking and analysis of ESME User-related events. Regular monitoring of the Event Viewer (Server) enhances system reliability and customer satisfaction.

Audit Logs:

The Audit Logs feature in iTextPRO records a comprehensive audit trail for various events executed by Admin and User Accounts. It captures events such as password recovery, property edits/updates/deletes, sender ID and template requests, ensuring a detailed account of system activities.

Key Details Included:
Username:
Identifies the specific account associated with the event.

Execution Date:
Records the date and time when the event took place.

IP Address:
Specifies the IP address from which the event was executed.

Event Type:
Classifies events, such as password recovery or property updates.

Benefits:
Comprehensive Tracking:
Monitors various actions performed within the system.

User Accountability:
Holds users accountable for their actions with detailed logs.

Security Enhancement:
Strengthens system security by tracking critical events.

Note: The Audit Logs provide a valuable tool for system administrators to review and analyze user activities, ensuring transparency, accountability, and system security.