Log Service
The log service improves system observability, allowing developers to quickly identify issues and enhance their development efficiency.
Last updated
The log service improves system observability, allowing developers to quickly identify issues and enhance their development efficiency.
Last updated
Scope: The log service aims to capture all key information within the system. Currently, gateway logs are included, with plans to expand coverage to Actionflows, database operations, deployment releases, and more in the future.
Storage Capacity: The log service offers varying storage capacities based on the project version, measured in days:
Free Plan: 1 day
Basic Plan: 7 days
Pro Plan: 30 days
Access the log service from the "Log Service" section on the project details page.
Utilize the following features for convenient log viewing:
Log Classification: Quickly view logs by category.
Query Statement Settings: Define time ranges and levels, and customize query syntax for precise log retrieval.
Bar Chart: Visual representation of log statistics; click the chart to set time ranges.
Log Details: Access detailed information; click on field values to add them to your query.
The log service offers efficient query syntax for flexible and rapid log searches.
Keyword Query: Enter a keyword to find logs containing that term.
Example: To find all requests related to the "account" table:
Field Query: Specify field values for targeted queries.
Example: To find logs where requestMethod is POST:
For text fields, wildcards (*) enable fuzzy searches.
Example: To find logs with traceId including 20241024:
Numeric fields can support range queries.
Example: To find logs with responseSize between 5000 and 10000:
Combined Conditional Queries: Use operators like 'and, or' to create complex queries.
Example: To find all logs related to account with status 200:
Multi-Level Queries: For fields that exist at multiple levels, provide the complete path.
Example: To find logs where the field query in requestBody contains mutation:
The Log Service records the running status of each node in the Actionflow in detail:
Each node generates two logs: a log when the node starts and a log when the node ends
A log is also generated when Context.log() is called within a code block
Explanation of node log fields
Field
Description
traceId
Used for event tracking query
nodeType
Type of the node
nodeName
Name of the node
version
Version of the Actionflow
input
Input of the node, including all referenceable data
output
Result of the node's execution
startAt
Start time of the node
endAt
End time of the node
Types of nodes in logs
Node
Type in Logs
Input
FLOW_START
Query Record
QUERY_RECORD
Update Record
UPDATE_RECORD
Insert Record
INSERT_RECORD
Delete Record
DELETE_RECORD
Code Block
CUSTUM_CODE
Add Role
ADD_ROLE_TO_ACCOUNT
Remove Role
REMOVE_ROLE_FROM_ACCOUN
Update Global Variables
UPDATE_GLOBAL_VARIABLES
Branch Start
BRANCH_SEPARATION
Branch End
BRANCH_MERGE
This category records all operations (add, delete, modify) on the database, including the following content:
Trigger method (frontend request, Actionflow, AI, etc.)
Detailed content of the operation
The project deployment and release process consists of various steps, and the log service will log information for each step, including:
Type of deployment (web, backend).
Status, start, and end times for each step.
Monitoring this information will aid in quickly resolving issues during deployment.
The gateway serves as a connection point between different networks, facilitating data forwarding for seamless communication. In the Momen platform, the following requests pass through the gateway:
Requests from frontend to backend.
Requests received via Callback.
Logs in this category encompass most requests, including CRUD operations on databases, APIs, and AI. However, due to system limitations, only outbound requests can be viewed; their results are not accessible.
