Understanding Log Types in Plinqx
In Plinqx, logs are categorized into different types to facilitate effective monitoring and troubleshooting of your integrations. Each log type serves a specific purpose, providing insights into various aspects of the transactions and operations within the platform. Recognizing and interpreting these log types is crucial for diagnosing issues, understanding system behavior, and ensuring the smooth functioning of your integrations. Below is a table that summarizes the various log types and their descriptions:
Log Types and Descriptions
| Log Type | Description |
|---|---|
| Info | Generic informational logs that include details such as the payload from external systems, URL endpoint, parameters, and transaction direction (Inbound/Outbound). |
| Debug | Logs generated as part of custom integration logic in Apex or Flows, useful for development and testing phases. |
| Error | System-generated logs that capture errors, such as schema validation failures, useful for identifying issues in integrations. |
| Action | Logs that record specific engine actions, like data transformation, providing insights into the operational aspects of transactions. |
Utilizing Log Information
By understanding and analyzing these log types, you can gain valuable insights into the performance and health of your integrations. Informational logs help in routine monitoring, while Debug logs are instrumental during development and troubleshooting. Error logs are critical for identifying and rectifying issues, and Action logs offer an overview of the operations carried out by the Plinqx platform. Together, these logs form an integral part of managing and optimizing your Plinqx integrations.