Logs

We use Elasticsearch for logging. We log all create, update, and delete operations; however, view operations are not logged. Logging is implemented in both resolvers and open API methods.

List of fields:

1. Initiator - shows the user’s name followed by their ID in parentheses (for example, Ethan Reynolds (65a52b15266d8cfb756ed675)). If no ID is provided, the placeholder text "NO_USER_SPECIFIED" or "-" will be used. For specific cases involving the transaction model, particularly in webhooks, the initiator can be "Fireblocks" or "Huntli."
   
   
2. Business model - refers to a distinct, independent model within our CRM, such as "Projects," "Settings," or "Client Area." A business model can also include submodules.
   
   
3. Sub model - specific model that belongs to a business model. For example, "Texts" is a sub model that belongs to the "Settings" business model.
   
   
4. Action - the type of operation being logged. The actions we track include "create," "update," "updateMany," and "delete."
   
   
5. Type - сan be either "internal" or "external." Internal logs are used for internal requests within resolvers, while external logs are associated with open API methods.
   
   
6. Sub type - defines whether the log is an "info" log or an "error" log. Typically, error logs are generated in the "catch" block of a "try-catch" construction, while info logs provide general informational messages.
   
   
7. Description - this field is used for providing additional details in specific cases where the standard information may not be sufficient. For example, in transaction webhooks, the description might include the current transaction status, such as "Sending transaction to Huntli," or detail a specific error, such as "Error while trying to send transaction to Huntli."
   
   
8. Error - is a stringified field containing the error message. It is used in the "catch" block of a "try-catch" construction, with a Sub type of "error."

Filters 

Use filters to narrow log entries by module, operation, source, and time.

Available filters:

1. Business model – Top-level system module (e.g. Desks, Projects, Clients, Businesses).

2. Action – Operation type: create, update, updateMany, delete.

3. Type – Log origin: internal (resolvers/system) or external (Open API, webhooks).

4. Sub type – Log level: info or error.

5. Created date – Date range when the log was generated.

Select one or more criteria and click Save to apply filters. Multiple filters can be combined to quickly isolate relevant logs for debugging, audits, or incident analysis.