- Overview
- Getting Started Guide
- UserGuide
-
References
-
ABEJA Platform CLI
- CONFIG COMMAND
- DATALAKE COMMAND
- DATASET COMMAND
- TRAINING COMMAND
-
MODEL COMMAND
- check-endpoint-image
- check-endpoint-json
- create-deployment
- create-endpoint
- create-model
- create-service
- create-trigger
- create-version
- delete-deployment
- delete-endpoint
- delete-model
- delete-service
- delete-version
- describe-deployments
- describe-endpoints
- describe-models
- describe-service-logs
- describe-services
- describe-versions
- download-versions
- run-local
- run-local-server
- start-service
- stop-service
- submit-run
- update-endpoint
- startapp command
-
ABEJA Platform CLI
- FAQ
- Appendix
describe-service-logs
Description
Describe service log information.
Synopsis
$ abeja model describe-service-logs [--help]
Usage: abeja model describe-service-logs [OPTIONS]
Get service log
Options:
-d, --deployment_id TEXT Deployment identifier [required]
-s, --service_id TEXT Service identifier [required]
--start_time TEXT Start time / 2017-01-01T00:00:00Z
--end_time TEXT End time / 2017-12-31T00:00:00Z
--next_token TEXT Next token
--help Show this message and exit.
Options
-d
, --deployment_id
Specify deployment_id when create-deployment is created.
-s
, --service_id
Specify service_id when create-service is created.
--start_time
Specify start time.
--end_time
Specify end time.
--next_token
Specify next_token included in the response.
Since log standard output is limited, next_token is included in the response when referring to an older log.
When there are few logs, next_token is not output.
Example
Describe of log information for the specified service
Command:
$ abeja model describe-service-logs --deployment_id 3456789012345 --service_id ser-4567890123456
Output:
{
"events": [
{
"message": "mesg: ttyname failed: Inappropriate ioctl for device",
"timestamp": "2017-09-01T00:00:00.000000+00:00"
},
...
]
}