OpenSVC |
|||||||||||||||||||||||||||||||||||||||||||||||||
actions viewUsageThis view displays the journal of all services events with their status. Main usage:
Screenshot![]() FieldsServiceService name the action applied to. Private collectors usually report shortnames, shared collectors usually report service names with domain names. AppThe application code is a way to group services dedicated/paid by some corporate entity or project. You can setup any application code you want in your services configuration file, using the app parameter. Responsible
NodeNode where the action has be executed. The node name is a link to the asset view. ActionThe executed action name. An action usually aggregates a number of log lines, plus a line with no log message as a header. The default action view has an 'empty' log filter active so you are presented only actions without their logs. You can drill down a specific action by clicking on its pid.
Status
BeginBegin timestamp of the action. EndEnd timestamp of the action. PidProcess identifier of the session handling the action on the node. Click to active a pid filter with this value. LogThe action log as it is displayed on the node standart output. |
|||||||||||||||||||||||||||||||||||||||||||||||||
|
Copyright © 2010 OpenSVC - Powered by web2py |
|||||||||||||||||||||||||||||||||||||||||||||||||