Application Launcher

Note

This page applies to only Cloud Classic. To access the content of this page, select Cloud Classic from the infrastructure list.

The Shell log records all commands that are executed by the application user. This includes SSH, cron, or user commands when executed in context of the site. This log is specific to Cloud Classic environments. It has a predefined format and can run Python, script, binary, or PHP.

Parsing the log file

The following line is a representative example of the data written into your website's Shell log:

Jan 9 20:51:28 web-1234 webapp[15605]: {"user": "webapp", "path": "/home/webapp", "pid": "15588", "user_session_id": "15588", "stage": "prod", "command": "ls", "status": "0"}

Each of the items in the Shell log is noted in the following table, along with its description:

Position	Field	Example	Description
0	date/time	`Jan 9 20:51:28`	The date and time when the command completes its execution. This is represented in the HTTP date/time format.
1	server	`web-1234`	The server from where the Shell command is run.
2	user	`webapp`	The user who runs the command.
3	pid	`15605`	The unique PID for the log.
4	user	`webapp`	The user who runs the command.
5	path	`/home/webapp`	The working directory for the command.
6	pid	`15588`	The PID (process ID) for the command that is run.
7	user_session_id	`15588`	The PID (process ID) for the Shell session that ran the command.
8	stage	`prod`	The stage of the site. For example, dev, prod.
9	command	`ls`	The full command.
10	status	`0`	The execution status or exit code of the Shell command. For example, `0` is the status code for success.

Note

This page applies to only Cloud Classic. To access the content of this page, select Cloud Classic from the infrastructure list.

Parsing the log file

The following line is a representative example of the data written into your website's Shell log:

Jan 9 20:51:28 web-1234 webapp[15605]: {"user": "webapp", "path": "/home/webapp", "pid": "15588", "user_session_id": "15588", "stage": "prod", "command": "ls", "status": "0"}

Each of the items in the Shell log is noted in the following table, along with its description:

Position	Field	Example	Description
0	date/time	`Jan 9 20:51:28`	The date and time when the command completes its execution. This is represented in the HTTP date/time format.

Note

This page applies to only Cloud Classic. To access the content of this page, select Cloud Classic from the infrastructure list.

Parsing the log file

The following line is a representative example of the data written into your website's Shell log:

Jan 9 20:51:28 web-1234 webapp[15605]: {"user": "webapp", "path": "/home/webapp", "pid": "15588", "user_session_id": "15588", "stage": "prod", "command": "ls", "status": "0"}

Each of the items in the Shell log is noted in the following table, along with its description:

Position	Field	Example	Description
0	date/time	`Jan 9 20:51:28`	The date and time when the command completes its execution. This is represented in the HTTP date/time format.
1	server	`web-1234`	The server from where the Shell command is run.
2	user	`webapp`	The user who runs the command.
3	pid	`15605`	The unique PID for the log.
4	user	`webapp`	The user who runs the command.
5	path	`/home/webapp`	The working directory for the command.
6	pid	`15588`	The PID (process ID) for the command that is run.
7	user_session_id	`15588`	The PID (process ID) for the Shell session that ran the command.
8	stage	`prod`	The stage of the site. For example, dev, prod.
9	command	`ls`	The full command.
10	status	`0`	The execution status or exit code of the Shell command. For example, `0` is the status code for success.

Parsing the log file

Parsing the log file

Parsing the log file

Did not find what you were looking for?

Did not find what you were looking for?

Shell logs

Parsing the log file

Shell logs

Parsing the log file

Shell logs

Parsing the log file

Did not find what you were looking for?

Did not find what you were looking for?