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. The Elasticsearch index for CRM is named "wicrm."??

List of fields:

• Initiator - this field contains the ID of the employee or client who initiated the action. If no ID is provided, the placeholder text "NO_USER_SPECIFIED" will be used. For specific cases involving the transaction model, particularly in webhooks, the initiator can be "Fireblocks" or "Huntli."
  
  
• 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.
  
  
• Sub model - specific model that belongs to a business model. For example, "Texts" is a sub model that belongs to the "Settings" business model.
  
  
• Action - the type of operation being logged. The actions we track include "create," "update," "updateMany," and "delete."
  
  
• 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.
  
  
• 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.
  
  
• 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."
  
  
• 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."