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 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 statusesConfiguration MongoDB logs rotation
        Configuration of system constants and directoriesarrow
      • Filtering bot actionsDirectory of gender markers
      Platform maintenancearrow
    • Personnel requirementsPlatform maintenance processesPlatform updatingPlatform service monitoringBackup and recoveryTransferring the platform to a new serverCreating, deleting, and populating tables for statistics in ClickHouseUsage of the aktool utilityUsers and directories engaged by the platform
      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 IDИнструкция по миграции истории в ClickHouseInstructions 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 accountDelete 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.

note

The following information is necessary :

  • RAM usage;
  • CPU usage;
  • disks ad free space;
  • opened files and connections.

Components​

NameDefault IPDefault port
MongoDB (control)
Single or cluster
127.0.0.127017
MongoDB (accounts)
Single or cluster
127.0.0.127018
SSDB (actions)127.0.0.14410
SSDB (hb)127.0.0.14420
SSDB (notify)127.0.0.14430
SSDB (stats)127.0.0.14440
RabbitMQ0.0.0.05672

Processes and services​

Platform executable files are located at {BASEDIR}/ak/bin.
PID-files are located at {BASEDIR}/pids.
Logs are located at {BASEDIR}/logs.

tip

For complete list of processes you can use {BASEDIR}/akd --processes.

Binary file nameProcess nameDefault IPDefault portDescription
adminwebcontrolAK:adminwebcontrol127.0.0.18081Web interface
akmtad
Can be moved to a remote host
AK:akmtad127.0.0.113444Mail transfer agent, AKMTA
apiAK:api127.0.0.18801API
cookie_saver
Can be moved to a remote host
AK:cookie_saver127.0.0.18099Visitor cookie processing
proctask
Can be moved to a remote host
AK:proctask127.0.0.18962Task processing, mailing launching
procactionsAK:procactions--Statistic events processing (opens, clicks)
proceventgenAK:proceventgen--Demo event generator
prochookAK:prochook--Action hooks
procpixelAK:procpixel--Pixel events processing
procintegrasAK:procintegras--External systems integration (AppMetrica etc.)
procleadsaverAK:procleadsaver--Import events processing
procnotifyAK:procnotify--Notifications processing

The process was removed in versions v2024.2.68.2.2206 and later; its functionality was migrated to proctask.
procpushAK:procpush--Push events processing
procresumeAK:procresume--Suspending and refreshing subscriptions
procrpcAK:procrpc127.0.0.18972RPC-client for internal connections
procsenderevAK:procsenderev--Events processing
procsmsevAK:procsmsev--SMS sending events processing
procsmslistenAK:procsmslisten127.0.0.18803SMS gateways events processing
proctriggerAK:proctrigger--Triggers processing
procwebverAK:procwebver--Email web versions processing
procworkflowAK:procworkflow127.0.0.16060Scenarios processing
pywebcontrolAK:pywebcontrol127.0.0.18080Proxying requests to webcontrol
stataggregatorAK:stataggregator--Statistics aggregator
tariffcontrollerAK:tariffcontroller--Tariff controller

The process was removed in versions v2024.2.68.2.2206 and later; its functionality was migrated to proctask.
trkaction
Can be moved to a remote host
AK:trkaction127.0.0.18095Tracking events registration
trk_amazon_sns
Can be moved to a remote host
AK:trk_amazon_sns127.0.0.18093Amazon MTA events registration
trkmandrill
Can be moved to a remote host
AK:trkmandrill127.0.0.18094Mandrill MTA events registration
trkimage
Can be moved to a remote host
AK:trkimage127.0.0.18096Pixel events registration
trkpush
Can be moved to a remote host
AK:trkpush127.0.0.18100Push events registration
trkread
Can be moved to a remote host
AK:trkread127.0.0.18097Email reads events registration
trksms
Can be moved to a remote host
AK:trksms127.0.0.18098SMS events registration
trkwebversion
Can be moved to a remote host
AK:trkwebversion127.0.0.18199Web-versions events registration
webcontrolAK:webcontrol127.0.0.18082User interface

Problem diagnostics​

Additionaly you can gather the required information and ask our team to help.

This page will give you the instructions.

Last updated on Jul 6, 2020
Previous
Platform updating
Next
Backup and recovery
  • Components
  • Processes and services
    • Problem diagnostics
© 2015 - 2026 Altcraft, LLC. All rights reserved.