# python.d\_job\_last\_collected\_secs

**URL:** <https://community.netdata.cloud/t/python-d-job-last-collected-secs/2036>\
**Category:** Alerts\
**Created:** [November 4, 2021, 12:53pm UTC](https://community.netdata.cloud/t/python-d-job-last-collected-secs/2036 "2021-11-04T12:53:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tasos\_Katsoulas](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/tasos_katsoulas/32/1344_2.png) [@Tasos\_Katsoulas](https://community.netdata.cloud/u/Tasos_Katsoulas)\
**Post date:** [November 4, 2021, 12:53pm UTC](https://community.netdata.cloud/t/python-d-job-last-collected-secs/2036/1 "2021-11-04T12:53:23Z")

</div>

# python.d\_job\_last\_collected\_secs

**Netdata | python.d.plugin**

The Netdata Agent also monitors itself, so this is an alert about the Netdata Python plugin. The Netdata Agent monitors the number of seconds since the last successful data collection for each of python plugin modules. This alert indicates that a specific module cannot reach the component it  
monitors to collect metrics from it.

You can see all the modules that are orchestrated by the python.d.plugin in [our GitHub repo](https://github.com/netdata/netdata/tree/master/collectors/python.d.plugin)

### Troubleshooting section

> **Check the Netdata logs**
>
> You need to identify why the Agent cannot collect metrics for a specific job. Inspect the Agent logs for this  
> specific job.
> 
> **Host machine:**
> 
> ```auto
> root@netdata # tail -f /var/log/netdata/error.log | grep <job> OR <module_name>
> 
> ```
> 
> **Docker:**
> 
> ```auto
> root@netdata # docker logs <netdata_container> 2>&1 | grep <job> OR <module_name>
> 
> ```
> 
> **Kubernetes:**
> 
> 1. Find the pod name of the node which produced the alert.
> 
> 2. Inspect it’s logs