# How to find the logs of my Netdata Agent

**URL:** <https://community.netdata.cloud/t/how-to-find-the-logs-of-my-netdata-agent/1044>\
**Category:** General\
**Tags:** agent, faq, how-to\
**Created:** [March 9, 2021, 3:46pm UTC](https://community.netdata.cloud/t/how-to-find-the-logs-of-my-netdata-agent/1044 "2021-03-09T15:46:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![OdysLam](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/odyslam/32/98_2.png) [@OdysLam](https://community.netdata.cloud/u/OdysLam)\
**Post date:** [March 9, 2021, 3:46pm UTC](https://community.netdata.cloud/t/how-to-find-the-logs-of-my-netdata-agent/1044/1 "2021-03-09T15:46:56Z")

</div>

To find the logs of your Netdata Agent, follow our [documentation](https://learn.netdata.cloud/docs/agent/daemon). To show them in the terminal for deugging purposes use: `less /var/log/netdata/error.log`.

When searching for a specific keyword, you can use `grep` to only output the lines that have that keyword, like `grep <keyword> /var/log/netdata/error.log`.

---

<div class="post-metadata">

**Author:** ![Thiago\_Marques\_0](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/thiago_marques_0/32/281_2.png) [@Thiago\_Marques\_0](https://community.netdata.cloud/u/Thiago_Marques_0)\
**Post date:** [March 10, 2021, 2:46pm UTC](https://community.netdata.cloud/t/how-to-find-the-logs-of-my-netdata-agent/1044/2 "2021-03-10T14:46:22Z")

</div>

To complement this awesome tip, I will also suggest users to use the option `-w` to get a more specific information, for example,

```auto
bash-5.1$ grep alert /var/log/netdata/error.log 
2021-03-10 14:15:21: go.d ERROR: prometheus[alertmanager_github_webhook_receiver_local] Get "http://127.0.0.1:9393/metrics": dial tcp 127.0.0.1:9393: connect: connection refused
2021-03-10 14:15:21: go.d ERROR: prometheus[alertmanager_github_webhook_receiver_local] check failed
2021-03-10 14:15:21: go.d ERROR: prometheus[alertsnitch_local] Get "http://127.0.0.1:9567/metrics": dial tcp 127.0.0.1:9567: connect: connection refused
2021-03-10 14:15:21: go.d ERROR: prometheus[alertsnitch_local] check failed
2021-03-10 14:15:22: go.d ERROR: prometheus[github_vulnerability_alerts_exporter_local] Get "http://127.0.0.1:9597/metrics": dial tcp 127.0.0.1:9597: connect: connection refused
2021-03-10 14:15:22: go.d ERROR: prometheus[github_vulnerability_alerts_exporter_local] check failed
2021-03-10 14:15:22: go.d ERROR: prometheus[alertmanager_silences_exporter_local] Get "http://127.0.0.1:9666/metrics": dial tcp 127.0.0.1:9666: connect: connection refused
2021-03-10 14:15:22: go.d ERROR: prometheus[alertmanager_silences_exporter_local] check failed
2021-03-10 14:15:22: go.d ERROR: prometheus[phabricator_webhook_for_alertmanager_local] Get "http://127.0.0.1:8292/metrics": dial tcp 127.0.0.1:8292: connect: connection refused
2021-03-10 14:15:22: go.d ERROR: prometheus[phabricator_webhook_for_alertmanager_local] check failed
2021-03-10 14:15:22: go.d ERROR: prometheus[telegram_bot_for_alertmanager_local] Get "http://127.0.0.1:9087/metrics": dial tcp 127.0.0.1:9087: connect: connection refused
2021-03-10 14:15:22: go.d ERROR: prometheus[telegram_bot_for_alertmanager_local] check failed
2021-03-10 14:15:22: go.d ERROR: prometheus[jiralert_local] Get "http://127.0.0.1:9097/metrics": dial tcp 127.0.0.1:9097: connect: connection refused
2021-03-10 14:15:22: go.d ERROR: prometheus[jiralert_local] check failed
bash-5.1$ grep -w alert /var/log/netdata/error.log 
bash-5.1$ 

```

As it is possible to see on this example, thanks the fact I did not have any message with `alert` word, the others were ignored. This is useful to look for plugin information.