Add documentation for accessing build logs. (#623)

* Add documentation for accessing build logs.
This commit is contained in:
Mustafa Demirhan 2018-04-11 09:47:44 -07:00 committed by GitHub
parent a1a3b8f2bd
commit 60d272b823
1 changed files with 5 additions and 4 deletions

View File

@ -112,15 +112,16 @@ your `Revision`:
kubectl get build $(kubectl get revision <revision-name> -o jsonpath="{.spec.buildName}") -o yaml kubectl get build $(kubectl get revision <revision-name> -o jsonpath="{.spec.buildName}") -o yaml
``` ```
The `conditions` in `status` provide the reason if there is any failure. The `conditions` in `status` provide the reason if there is any failure. To access build logs, first execute `kubectl proxy` and then open [Kibana UI](http://localhost:8001/api/v1/namespaces/monitoring/services/kibana-logging/proxy/app/kibana). Use any of the following filters within Kibana UI to see build logs. _(See [telemetry guide](../telemetry.md) for more information on logging and monitoring features of Elafros.)_
* All build logs: `_exists_:"kubernetes.labels.build-name"`
* Build logs for a specific build: `kubernetes.labels.build-name:"<BUILD NAME>"`
* Build logs for a specific build and step: `kubernetes.labels.build-name:"<BUILD NAME>" AND kubernetes.container_name:"build-step-<BUILD STEP NAME>"`
## Check application logs ## Check application logs
Elafros provides default out-of-box logs for your application. After executing Elafros provides default out-of-box logs for your application. After executing
`kubectl proxy`, you can go to the `kubectl proxy`, you can go to the
[Kibana UI](http://localhost:8001/api/v1/namespaces/monitoring/services/kibana-logging/proxy/app/kibana) [Kibana UI](http://localhost:8001/api/v1/namespaces/monitoring/services/kibana-logging/proxy/app/kibana)
to search for logs. You need to do create an index when you open Kibana for the to search for logs. _(See [telemetry guide](../telemetry.md) for more information on logging and monitoring features of Elafros.)_
first time. See this [instruction](../telemetry.md) for details.
### Stdout/stderr logs ### Stdout/stderr logs