[pve-devel] [PATCH docs 4/4] Add monitoring & troubleshooting section

[Thomas Lamprecht]

On 4/3/19 4:23 PM, Alwin Antreich wrote:
> To give a little overview on where to look if trouble arise.
> 
> Signed-off-by: Alwin Antreich <a.antreich at proxmox.com>
> ---
>  pveceph.adoc | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/pveceph.adoc b/pveceph.adoc
> index b7378d5..7db2039 100644
> --- a/pveceph.adoc
> +++ b/pveceph.adoc
> @@ -580,6 +580,30 @@ with:
>  pveceph pool destroy NAME
>  ----
>  
> +
> +Ceph monitoring & troubleshooting
> +---------------------------------
> +A good start is to monitor the ceph health to begin with. Either through the
> +ceph tools itself or also by accessing the status through the {pve}
> +link:api-viewer/index.html[API].
> +
> +If the cluster is in an unhealthy state the commands below will give an
> +overview on the current events.
> +
> +----
> +ceph -s
> +ceph -w
> +----
> +
> +To get a more detailed view, every ceph service has a log file under
> +`/var/log/ceph/` and if there is not enough detail, the log level can be
> +adjusted footnote:[Ceph log and debugging http://docs.ceph.com/docs/luminous/rados/troubleshooting/log-and-debug/].
> +
> +You can find more information about troubleshooting
> +footnote:[Ceph troubleshooting http://docs.ceph.com/docs/luminous/rados/troubleshooting/]
> +a Ceph cluster on its website.
> +
> +
>  ifdef::manvolnum[]
>  include::pve-copyright.adoc[]
>  endif::manvolnum[]
> 

applied, with followup (e.g., referencing the HEALT_OK, _WARN, .. stuff), thanks!