Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guide iconUser guide
Developer guide iconDeveloper guide
Admin guide iconAdmin guide
English
  • Русский
  • English
Login
    Getting StartedAdministrator documentationFunctional characteristics
      Technology descriptionarrow
    • Architecture OverviewComponent Description
        Deployment schemesarrow
      • Basic schemeFail-safe schemeTypical Placement in Infrastructure
    System requirements
      Admin Panelarrow
      • Account areaarrow
        • Accountsarrow
        • Account UsersAccount Virtual SendersAccount Database Indexes
        TariffsExternal data configurationLDAPTasksSchedule JobsGlobal Stop ListsWebversion Store Policies
        Settingsarrow
      • Databases
          Accessarrow
        • AdminsAPI tokens
        Notifiers
          MTAarrow
        • Default rulesRetry rulesLock rulesBounce patternsStrategiesKeysISPsPools
      Nodes
        Sendersarrow
      • EmailSMSEvent generatorIntegration with Altcraft Cloud SMTPIntegration with SendsayENS: настройка сендера
        Reportsarrow
      • Audit JournalData Usage
        Toolsarrow
      • ARF decoderURL decoderSMID decoderLicense
      Platform installationarrow
    • Automatic installationManual installationRunning the platform in a Docker container
      Platform configurationarrow
    • Configuration fileDomain settingsLDAP access configurationSending Email via SMTP relayPixel and push domain configurationCluster and Replication SetupSystem notifications configurationProcesses UNIX sockets configurationHTTPS ConfigurationMigrating from MongoDB Community Edition to Percona Server for MongoDBAdding sender IP addressesDeduplication request settingsPostgreSQL database for account dataProxy server settingsKeycloak Integration with AltcraftGetting HTTP service statusesConfiguring MongoDB log rotation
        Configuration of system constants and directoriesarrow
      • Filtering bot actionsDirectory of gender markers
      Platform maintenancearrow
    • Personnel requirementsPlatform maintenance processesPlatform updatingBackup and recoveryTransferring the platform to a new serverCreating, deleting, and populating tables for statistics in ClickHouseUsing the aktool utilityUsers and directories engaged by the platformPlatform service monitoring
      Custom channels guidearrow
    • OverviewCreating and configuring a channelEntity field configurationTemplate languageEntities
        Pipesarrow
      • Pipe: Basic ConceptsResultErrorsLogPackUnpackHTTP RequestStore SetStore GetSelectorSQLEventerScheduler
        Pipelinesarrow
      • Pipeline: Basic ConceptsMessageScheduleListenerModerateStop
      Extraarrow
    • System page customizationSend Message IDClickHouse History Migration GuideInstructions for migrating history to ClickHouseUtility for importing push subscriptions to Firebase projectUtility for importing push subscriptions to Firebase project
    Processing HTTP/HTTPS traffic
      Administrator APIarrow
      • Accounts admin apiarrow
        • Restricted accessarrow
        • Account Activation and DeactivationAccount Freeze and Unfreeze
        Get accounts listAdd a new accountDelete the account
        Account usersarrow
      • Update an Existing AccountAdd a new userDelete a userGet a list of usersSending a Welcome Email
        Nodesarrow
      • Synchronize node MTA configurationGet nodes listGet node MTA statusActivate node MTADeactivate node MTA
        Senders admin apiarrow
      • Create or update AKMTA senderGet AKMTA sender informationAssign account to senderGet senders listDelete senderRestore sender
          Sender queuearrow
        • Get sender queue informationHold sender queueRelease sender queueClear sender queue
        Virtual sendersarrow
      • Get virtual senders listGet virtual sender informationCreate virtual senderUpdate virtual senderClone virtual senderDelete virtual sender
    Documentation Archive
  • Platform maintenance
  • Platform service monitoring

Platform service monitoring

Depending on the monitoring system used in the organization, a specialist must choose a method for monitoring the status of platform processes.

The page describes all the processes that need to be kept in working order for the platform to fully operate.

We recommend checking for the existence of a process by name using the tools built into the monitoring system or using the pidof utility.

The following information must be collected for each host (or virtual machine):

  • RAM usage and available memory;
  • CPU usage and available CPU time;
  • Available disk space and disk utilization information (speed, latency, SMART);
  • Number of open files and connections.

Databases and services​

Default IPDefault portImportanceAlert
MongoDB127.0.0.127017CriticalUnable to establish TCP connection
ClickHouse127.0.0.19000CriticalUnable to establish TCP connection
SSDB (hb)127.0.0.14420CriticalUnable to establish TCP connection
SSDB (notify)127.0.0.14430CriticalUnable to establish TCP connection
RabbitMQ0.0.0.05672CriticalUnable to establish TCP connection

RabbitMQ queues​

Virtual hostQueue nameProducerConsumerDescriptionImportanceAlert
altcraftoxy_triggers*AK:proctriggerTriggers (mailings)HighMinimum number of messages in queue >= 10000 over 10 minutes
altcraftoxy_triggers_prior*AK:proctriggerPriority triggers (mailings)HighMinimum number of messages in queue >= 5000 over 10 minutes
altcrafttrk_*AK:trk*
AK:cookie_saver
procactions
procpixel
Events processed by trackingsHighMinimum number of messages in queue >= 5000 over 10 minutes
altcraftakmta_*AK:proctrigger
AK:webcontrol
campaign
AK:procworkflow
AK:akmtadMessages for sendingHighNumber of messages does not decrease over 50 minutes
altcraftgeo_akmta_*AK:proctrigger
AK:webcontrol
campaign
AK:procworkflow
AK:akmtadMessages for sending by time zonesHighNumber of messages does not decrease over 50 minutes
altcraftprior_akmta_*AK:proctrigger
AK:webcontrol
campaign
AK:procworkflow
AK:akmtadPriority messages for sendingHighNumber of messages does not decrease over 50 minutes

AKD processes​

To verify platform operability, it is sufficient to ensure the presence of the process in the virtual filesystem /proc.

The full list of processes can be viewed with the command – <BASEDIR>/akd --processes

The default PID file location is – <BASEDIR>/pids/<Executable file name>.pid

Executable file nameProcess nameDescriptionImportanceAlert
webadminAK:webadminAdmin panelMediumProcess not found in the virtual filesystem /proc
akmtadAK:akmtadMail transfer agent, AKMTAHighProcess not found in the virtual filesystem /proc
apiAK:apiAPIHighProcess not found in the virtual filesystem /proc
cookie_saverAK:cookie_saverUser cookie processingHighProcess not found in the virtual filesystem /proc
proctaskAK:proctaskTask execution, mailing launchHighProcess not found in the virtual filesystem /proc
procactionsAK:procactionsEvent processing for statistics (clicks, opens, subscriptions, etc.)HighProcess not found in the virtual filesystem /proc
proceventAK:proceventEvent processing and writing to ClickHouseHighProcess not found in the virtual filesystem /proc
prochookAK:prochookCapturing various events from the platformHighProcess not found in the virtual filesystem /proc
procpixelAK:procpixelPixel events processingHighProcess not found in the virtual filesystem /proc
procintegrasAK:procintegrasIntegration with external systems (AppMetrica, etc.)HighProcess not found in the virtual filesystem /proc
procleadsaverAK:procleadsaverImport statistics processingMediumProcess not found in the virtual filesystem /proc
procnotifyAK:procnotifyNotification processing

The process was removed in versions v2024.2.68.2.2206 and later; its functionality was migrated to proctask
MediumProcess not found in the virtual filesystem /proc
procpushAK:procpushPush events processingHighProcess not found in the virtual filesystem /proc
procresumeAK:procresumeProcessing and database scanning to restore profile statusMediumProcess not found in the virtual filesystem /proc
procrpcAK:procrpcRPC client for processing RPC connections with processesHighProcess not found in the virtual filesystem /proc
procsenderevAK:procsenderevEvent processingHighProcess not found in the virtual filesystem /proc
procsmsevAK:procsmsevRequests information on SMS sendingsHighProcess not found in the virtual filesystem /proc
procsmslistenAK:procsmslistenProcessing responses from SMS gatewaysHighProcess not found in the virtual filesystem /proc
proctriggerAK:proctriggerTrigger mailing processingHighProcess not found in the virtual filesystem /proc
procwebverAK:procwebverWeb versions processingMediumProcess not found in the virtual filesystem /proc
procworkflowAK:procworkflowScenarios processingHighProcess not found in the virtual filesystem /proc
tariffcontrollerAK:tariffcontrollerSending limit control (tariffs)

The process was removed in versions v2024.2.68.2.2206 and later; its functionality was migrated to proctask
MediumProcess not found in the virtual filesystem /proc
trkactionAK:trkactionTracking event registrationHighProcess not found in the virtual filesystem /proc
trk_amazon_snsAK:trk_amazon_snsAmazon sender event registrationHighProcess not found in the virtual filesystem /proc
trkmandrillAK:trkmandrillMandrill sender event registrationHighProcess not found in the virtual filesystem /proc
trkimageAK:trkimagePixel events registrationHighProcess not found in the virtual filesystem /proc
trkpushAK:trkpushPush tracking events registrationHighProcess not found in the virtual filesystem /proc
trkreadAK:trkreadEmail message read events registrationHighProcess not found in the virtual filesystem /proc
trksmsAK:trksmsSMS message read events registrationHighProcess not found in the virtual filesystem /proc
trkwebversionAK:trkwebversionWeb version read events registrationHighProcess not found in the virtual filesystem /proc
webcontrolAK:webcontrolUser web interfaceHighProcess not found in the virtual filesystem /proc

CPU time​

https://en.wikipedia.org/wiki/CPU_time

Metric typeDescriptionImportanceAlert
CPU system timeCPU usage by process in percent (system)Info-
CPU iowait timeCPU usage by process in percent (iowait)High> 15% * number of vCPU cores
CPU user timeCPU usage by process in percent (user)Info-
CPU utilizationCPU usage by process in percent (total)High> 50% * number of vCPU cores

Memory​

Metric typeDescriptionImportanceAlert
RSS (resident set size)https://en.wikipedia.org/wiki/Resident_set_sizeHigh> 20% of total memory
SWAPhttps://en.wikipedia.org/wiki/Paging#Unix_and_Unix-like_systemsHigh> 5% of total SWAP

Network​

To identify network issues, it is recommended to monitor the number of connections for each state. https://en.wikipedia.org/wiki/Transmission_Control_Protocol#Protocol_operation

Metric typeDescriptionImportanceAlert
CLOSEClosed. Socket is not in use.Info-
CLOSE_WAITRemote side has disconnected; waiting for socket closure.MediumNumber of connections > 5000
CLOSINGSocket closed, then remote side disconnected; waiting for acknowledgment.Info-
ESTABLISHEDConnection established.MediumNumber of connections > 25000
FIN_WAIT1Socket closed; connection disconnecting.Info-
FIN_WAIT2Socket closed; waiting for remote side disconnect.Info-
LAST_ACKRemote side disconnected, then socket closed; waiting for acknowledgment.Info-
LISTENWaiting for incoming connections.Info-
SYN_RECVInitial connection synchronization in progress.Info-
SYN_SENTActively attempting to establish connection.HighNumber of connections > 5000
TIME_WAITSocket closed, but waiting for packets still in the network for processingHighNumber of connections > 5000
Last updated on May 26, 2026
Previous
Users and directories engaged by the platform
Next
Custom channels guide
  • Databases and services
    • RabbitMQ queues
  • AKD processes
    • CPU time
    • Memory
    • Network
© 2015 - 2026 Altcraft, LLC. All rights reserved.