Monitoring Project Status
Use the streamingclusteradmin --get_projects command to monitor the status of your projects.
streamingclusteradmin --uri=esps://<host>:<port> --username=<username> --password=<password> --get_projectsFor each project, --get_projects provides two types of statuses: requested status and current status.
The requested status is the desired status that the project is attempting to achieve. This status can be one of the following:
| Requested Status | Description |
|---|---|
| Started-Running | The project is fully functional. |
| Stopped | The project is stopped entirely. |
When the project is requested to start or stop, the requested status becomes started-running or stopped, respectively. The project then goes through a cycle of starting up or shutting down. The cycle is not instantaneous.
The current status is the actual status at the time of the report. This status can be one of the following:
| Current Status | Description |
|---|---|
| Starting | The project has received a request to start, but the process has not started yet. |
| Started | The controller has received the request and is about to start the project. The requested status is started-running. |
| Started-Initializing | The project process has started and is in contact with the cluster, but it is not yet functional. The requested status is started-running. |
| Started-Running | The project is fully functional. The requested status is started-running. |
| Stopping | The project has received a request to stop, but the shutdown cycle is not complete yet. The request status will be stopped. |
| Stopped | The project is stopped. The request status is stopped. |
| Failed | The project achieved started-running status, but it has suddenly stopped without a stop request. The requested status is started-running. |
| Start-Failed | An attempt was made to start the project, but the project never achieved started-running status. The requested status is started-running. |
Use the --get_projects command in either command line mode or interactive mode. For further instruction, consult the Server Executables section of the SAP Event Stream Processor: Utilities Guide.
If your project fails for any reason, review the project base directory, examining the esp_server.log, stdstreams.log, and cluster.log of that project for reported errors. Project logs are stored in different directories depending on whether the project is deployed on a local or remote cluster. For more information on log files, consult the File and Directory Infrastructure and Project Logging sections of the SAP Event Stream Processor: Configuration and Administration Guide. For information on troubleshooting project errors, consult the Troubleshoot A Cluster section of the SAP Event Stream Processor: Configuration and Administration Guide.