# Diagnostic Methods For Tikv Server Oom

+ logs
  + `dmesg -T | grep tikv-server` The results have a log of the OOM-killer at a time near the incident
  + Tikv.log (log of “Welcome to TiKV” for the time near after the accident < 即 TiKV server 发生重启 >)
+ Grafana monitoring
  + `TiKV - Details --> Cluster --> Memory` 

![left](./student-guide/diagram/24-Diagnostic-methods-of-OOM-01-01.png)

------------------------------------------------------------

TiKV Server OOM can confirm whether OOM has occurred in the following ways:
- Logs
  - operating system
    - dmesg -T | grep tikv-server results have logs of the OOM-killer at the time near the incident.
  - tikv.log 
    - Grep to the log of “Welcome to TiKV” near the time after the incident (i.e. the TiKV server restart).
- Grafana monitoring
  - TiKV - Details —> Cluster —> Memory, you can observe the TiKV Server instance, which shows a rapid increase in memory and then a rapid decline, and the memory monitoring of the TiKV Server shows a discontinuous state