knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Copy edits to debugging-application-issues.md (#178)

This commit is contained in:
Peter Delaney 2018-07-18 10:32:31 -07:00 committed by Google Prow Robot
parent 256e571cfb
commit 6f3490b28d
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
serving/debugging-application-issues.md
View File

@ -1,12 +1,12 @@
# Debugging Issues with Your Application
You deployed your app to Knative Serving, but it isn't working as expected.
Go through this step by step guide to understand what failed.
Go through this step-by-step guide to understand what failed.
## Check command line output
## Check command-line output
Check your deploy command output to see whether it succeeded or not. If your
deployment process was terminated, there should be an error message showing up
deployment process was terminated, you should see an error message
in the output that describes the reason why the deployment failed.
This kind of failure is most likely due to either a misconfigured manifest or
@ -54,13 +54,13 @@ kubectl get configuration <configuration-name> -o jsonpath="{.status.latestCreat
If you configure your `Route` with `Revision` directly, look up the revision
name in the `Route` yaml file.
Then run
Then run the following command:
```shell
kubectl get revision <revision-name> -o yaml
```
A ready `Revision` should has the following condition in `status`:
A ready `Revision` should have the following condition in `status`:
```yaml
conditions:
@ -91,7 +91,7 @@ To get the `Pod`s for all your deployments:
kubectl get pods
```
This should list all `Pod`s with brief status. For example:
This command should list all `Pod`s with brief status. For example:
```text
NAME READY STATUS RESTARTS AGE
@ -118,7 +118,7 @@ your `Revision`:
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. To
If there is any failure, the `conditions` in `status` provide the reason. 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