It is currently not technically possible to automatically assign host processes and their services to a software application. Versio.io allows customers to define the application context for processes and services in an environment variable
The environment variable for application assignment can be defined at the following levels: * Host level - application mapping applies to all processes and services on the host. The assignment on host level is only conditionally recommended, because all captured host processes and services are assigned to an application by Versio.io (too rough). * Process level - application mapping applies to the process instance and all services provided by it. * Shell/Bash level - application mapping applies to all processes and services in the dedicated execution context.
The mapping is done in a defined format
Application(Service), which for simplicity is illustrated in the following table in the form of examples.
Specifying services reduces the mapping to an application only for the specified services. For example, the databases of a database management system can be assigned to different applications.
|One application and one service||
|One application and specific services||
|Assignment to multiple applications and specific services||
The following topology shows an example of how processes and specific services have been assigned to an application.
Figure:Example topology for which the processes and services are assigned to an application
Shell script or batch file
export VERSIO_APPLICATION_ID="crm.my-domain.com" bash my-app
docker run -d -e VERSIO_APPLICATION_ID="crm.my-domain.com" my-docker-image:latest
version: "3" services: crm: image: mycrm/mycrm:latest environment: - VERSIO_APPLICATION_ID="crm.my-domain.com" ports: - 443:443
Linux systemd service
[UNIT] ... [Service] Environment="VERSIO_APPLICATION_ID=crm.my-domain.com" ... [INSTALL] ...