![]() The summary view is useful if you have a long running job and it is not important to view detail about its progress nor the log messages. The summary view is the left most tab in the execution page and provides a simplified view of the execution state. The "Save as a Job." button offers a user to create a job from the command using the same node filter info and automatically defines the first step of the workflow using the command string.Command executions display the command string as the execution name and an icon that looks like a terminal command prompt ( >_).An Action menu provides actions to modify the job. Job executions show the Job name and group and display an icon that looks like a book. There are small differences between the two though and the Rundeck graphic interface indicates this through a few changes to the appearance in the web pages. Whether executing a job or a command, Rundeck provides a consistent interface to the execution. The state also contains information about start and end time, and who started it.īesides the graphical interface, it is also possible to view an execution via the API or command line tool. The execution state consists of metadata about the steps, nodes where steps are running, log output, and any inputs and options the job runner has provided. Jobs can complete either successfully, with a failure, partial success or have been aborted. The Rundeck graphical interface lets you watch the progress of an execution in a number of ways - summary, monitor, log view or status bar - depending on the level of detail you desire. ![]() You can share this URL to other Rundeck users and all see a common view of the execution. Each execution is identified by an ID and is addressable by a unique URL. Users can view an execution while it is in one of two states, running or completed. # OverviewĪn execution represents the state of a command or job execution. ![]() The data about the execution is used in rundeck to monitor the progress of a job or command and later for reporting about what happened.Įach execution contains any output generated by commands or job steps, a record of the nodes where they occurred and the start/end time and status for each step. That allows you to completely replay a session using cat screenlog.0 but can also make the filesize huge and complicate parsing the file in scripts.An execution is a representation of the activity of a running or completed command or job. When a running command inside the screen session is inline updating lines, by using the \r or carriage return character to make it look like an animation, all of those changes including the erased characters are being saved in the log file. One thing to keep in mind though: all screen output is being written to the file. Tail -Fn 0 screenlog.0 | ccze | grep -i error Note When tailing the log you can combine more magic, like parsing the output with colorizer ccze for improved readability, or use grep to only display the lines you are interested in. -n 0 means to only watch, don’t output older lines.-F sets tail to keep watching the file for changes.Otherwise you have only typed the command without hitting enter. ^M sends a CTRL + M key combination to the session.logfile flush tells the screen to set the log interval time in seconds.colon tells the session an internal command is coming up. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |