Description: This tool provides a detailed record of all communications (API calls) that occurred between the Framework360 system and external services or vice versa.
What is it for? (Practical examples)
Use this tool to have full visibility over automatic operations and integrations.
- Integration verification: Quickly check the status (OK or ERROR) of an external transaction, such as sending data to a CRM or processing a payment.
- Error diagnosis: If an automatic process does not work, you can analyze the log to see exactly which data was sent and which error messages were received from the external service.
- Origin tracking: Identify the IP address and origin of an external request that interacted with your system.
Main features
1. Historical Log View
The main screen shows a summary table of all recorded calls.
- Status: Indicates whether the communication was successfully completed (
OK) or encountered a problem (ERROR). - Description (Endpoint): Shows the address or specific service that was called or that called the system.
- IP: The IP address associated with the request.
- Date: Exact date and time when the interaction occurred.
2. Detailed Call Analysis
By selecting a row from the table, you can access the detailed view that provides all data related to that specific interaction.
- General Details: Shows the Endpoint, exact Time, IP Address, and Origin of the request (for example, whether it was a direct call or came from another part of the system).
- User Agent: Information about the software or device that made the request.
- Request Body: Displays the exact data that the system sent to the external service (or received, depending on the type of call).
- Response Body: Displays the exact data received in response from the external service. This data is crucial to understand if the operation was successful and to analyze any error messages.
3. Log Management
You can manage the recorded data directly from the main table:
- Viewing: Open the call details (as described above).
- Deletion: Remove individual entries from the historical log.
Automatic integrations
This module does not require manual configuration by the user. It works as a passive logging system:
- Automatic recording: Every time the system interacts with an external service via API (for example, to synchronize data or send notifications), the event is automatically recorded in this monitor, providing a complete trace of the operation.
