API Logs
Introduction
Begin by addressing the significance of API logs in the context of robotics.
Emphasize the role of logs in monitoring robotic systems and ensuring their security and efficiency.
Availability of API Logs:
Explain that API logs are accessible for customers using the Unified module alongside Business Plans.
Clarify that the roles with access include Owner, Supervisor, and Bot Builder.
Instruct on navigating to the API Logs via the App Integrations Section.
Call Logs History
Mention that the history of call logs is maintained for the last 7 days, and error codes for the last 30 days.
Functionality and Supported Integrations:
List the integrations relevant to robotics, such as Engati APIs, JSON API Node, and API Triggers.
Highlight that all interactions with robotic platforms are logged and available for review.
Searching API Logs
Describe the search functionality, which allows users to filter and find specific API logs.
Stress the importance of this feature in troubleshooting robotic systems.
Detailed Analysis
Discuss the comprehensive analysis available for each call log, which is crucial for understanding robotic operations.
Cover the types of information stored, such as Status, Bot name, Source, User, Application, Timestamp, and Request and Response Body.
Logs for Script Node
Explain how script node errors can be tracked, which is essential for debugging robotic software.
Filters:
Justify the necessity of filters due to the volume of log data generated by robotic systems.
Outline the filters available, such as Response Status, Request Type, Response Code, Bot Name, and Dates.
Notification Emails
Inform that in case of errors affecting robotic operations, notification emails are sent to the Owner’s email.
Add that these notifications can be configured for other user roles as well.
Reauthorise Workflow
Discuss the reasons for disintegration of integrations affecting robotic systems and how the Reauthorise button helps in restoring them.
Conclusion
Offer assistance for any issues related to robotic integrations and provide the support email address.
Closing:
Conclude by emphasizing the importance of API logs in maintaining robust and secure robotic systems.