# Troubleshooting useless/misleading NGINX "number of seconds since the last successful data collection" alerts?

**URL:** <https://community.netdata.cloud/t/troubleshooting-useless-misleading-nginx-number-of-seconds-since-the-last-successful-data-collection-alerts/5377>\
**Category:** Help\
**Created:** [April 22, 2024, 8:29pm UTC](https://community.netdata.cloud/t/troubleshooting-useless-misleading-nginx-number-of-seconds-since-the-last-successful-data-collection-alerts/5377 "2024-04-22T20:29:59Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_F](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ryan_f/32/3403_2.png) [@Ryan\_F](https://community.netdata.cloud/u/Ryan_F)\
**Post date:** [April 22, 2024, 8:29pm UTC](https://community.netdata.cloud/t/troubleshooting-useless-misleading-nginx-number-of-seconds-since-the-last-successful-data-collection-alerts/5377/1 "2024-04-22T20:29:59Z")

</div>

Thank you for any and all help. This is actually happening on several servers somewhat randomly, and they are false positives in the sense that the service NGINX is running proper.

## Problem/Question

Getting regular alerts for NGINX:  
Escalated to Critical, NGINX = 1213 seconds ago, on server.host.name  
number of seconds since the last successful data collection

## Relevant docs you followed/actions you took to solve the issue

Unable to find any documentation

## Environment/Browser/Agent’s version etc

ackaging:  
Netdata Version \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : v1.45.3  
Installation Type \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : binpkg-rpm  
Package Architecture \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : x86\_64  
Package Distro \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ :  
Configure Options \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : dummy-configure-command  
Default Directories:  
User Configurations \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : /etc/netdata  
Stock Configurations \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : /usr/lib/netdata/conf.d  
Ephemeral Databases (metrics data, metadata) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : /var/cache/netdata  
Permanent Databases \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : /var/lib/netdata  
Plugins \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : /usr/libexec/netdata/plugins.d  
Static Web Files \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : /usr/share/netdata/web  
Log Files \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : /var/log/netdata  
Lock Files \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : /var/lib/netdata/lock  
Home \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : /var/lib/netdata  
Operating System:  
Kernel \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : Linux  
Kernel Version \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : 4.18.0-513.11.1.lve.el8.x86\_64  
Operating System \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : CloudLinux  
Operating System ID \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : cloudlinux  
Operating System ID Like \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : rhel fedora centos  
Operating System Version \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : 8.9 (Anatoly Levchenko)  
Operating System Version ID \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : none  
Detection \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : /etc/os-release  
Hardware:  
CPU Cores \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : 32  
CPU Frequency \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : 2600000000  
RAM Bytes \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : 126162604032  
Disk Capacity \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : 1717986918400  
CPU Architecture \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : x86\_64  
Virtualization Technology \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : kvm  
Virtualization Detection \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : systemd-detect-virt  
Container:  
Container \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : none  
Container Detection \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : systemd-detect-virt  
Container Orchestrator \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : none  
Container Operating System \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : none  
Container Operating System ID \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : none  
Container Operating System ID Like \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : none  
Container Operating System Version \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : none  
Container Operating System Version ID \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : none  
Container Operating System Detection \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : none  
Features:  
Built For \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : Linux  
Netdata Cloud \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Health (trigger alerts and send notifications) \_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Streaming (stream metrics to parent Netdata servers) \_\_\_\_\_\_\_ : YES  
Back-filling (of higher database tiers) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Replication (fill the gaps of parent Netdata servers) \_\_\_\_\_\_ : YES  
Streaming and Replication Compression \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES (zstd gzip)  
Contexts (index all active and archived metrics) \_\_\_\_\_\_\_\_\_\_\_ : YES  
Tiering (multiple dbs with different metrics resolution) \_\_\_ : YES (5)  
Machine Learning \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Database Engines:  
dbengine \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
alloc \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
ram \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
none \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Connectivity Capabilities:  
ACLK (Agent-Cloud Link: MQTT over WebSockets over TLS) \_\_\_\_\_ : YES  
static (Netdata internal web server) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
h2o (web server) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
WebRTC (experimental) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : NO  
Native HTTPS (TLS Support) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
TLS Host Verification \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Libraries:  
LZ4 (extremely fast lossless compression algorithm) \_\_\_\_\_\_\_\_ : NO  
ZSTD (fast, lossless compression algorithm) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
zlib (lossless data-compression library) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Brotli (generic-purpose lossless compression algorithm) \_\_\_\_ : NO  
protobuf (platform-neutral data serialization protocol) \_\_\_\_ : YES (system)  
OpenSSL (cryptography) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
libdatachannel (stand-alone WebRTC data channels) \_\_\_\_\_\_\_\_\_\_ : NO  
JSON-C (lightweight JSON manipulation) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
libcap (Linux capabilities system operations) \_\_\_\_\_\_\_\_\_\_\_\_\_\_ : NO  
libcrypto (cryptographic functions) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
libyaml (library for parsing and emitting YAML) \_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Plugins:  
apps (monitor processes) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
cgroups (monitor containers and VMs) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
cgroup-network (associate interfaces to CGROUPS) \_\_\_\_\_\_\_\_\_\_\_ : YES  
proc (monitor Linux systems) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
tc (monitor Linux network QoS) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
diskspace (monitor Linux mount points) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
freebsd (monitor FreeBSD systems) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : NO  
macos (monitor MacOS systems) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : NO  
statsd (collect custom application metrics) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
timex (check system clock synchronization) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
idlejitter (check system latency and jitter) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
bash (support shell data collection jobs - charts.d) \_\_\_\_\_\_\_ : YES  
debugfs (kernel debugging metrics) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
cups (monitor printers and print jobs) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
ebpf (monitor system calls) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
freeipmi (monitor enterprise server H/W) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
nfacct (gather netfilter accounting) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : NO  
perf (collect kernel performance events) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
slabinfo (monitor kernel object caching) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Xen \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : NO  
Xen VBD Error Tracking \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : NO  
Logs Management \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Exporters:  
AWS Kinesis \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : NO  
GCP PubSub \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : NO  
MongoDB \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Prometheus (OpenMetrics) Exporter \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Prometheus Remote Write \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Graphite \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Graphite HTTP / HTTPS \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
JSON \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
JSON HTTP / HTTPS \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
OpenTSDB \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
OpenTSDB HTTP / HTTPS \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
All Metrics API \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Shell (use metrics in shell scripts) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : YES  
Debug/Developer Features:  
Trace All Netdata Allocations (with charts) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : NO  
Developer Mode (more runtime checks, slower) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ : NO

## What I expected to happen

No alerts are expected, as NGINX is working properly.

---

<div class="post-metadata">

**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\
**Post date:** [April 23, 2024, 9:51am UTC](https://community.netdata.cloud/t/troubleshooting-useless-misleading-nginx-number-of-seconds-since-the-last-successful-data-collection-alerts/5377/2 "2024-04-23T09:51:05Z")

</div>

Hi, @Ryan_F.

> Escalated to Critical, NGINX = 1213 seconds ago, on server.host.name

What alarm are you referring to? Can you provide the alarm/template name? The latest stable version of Netdata is v1.45.3 and nginx last collected alarm was removed in v1.32.0 (2.5 years ago).

---

<div class="post-metadata">

**Author:** ![Ryan\_F](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ryan_f/32/3403_2.png) [@Ryan\_F](https://community.netdata.cloud/u/Ryan_F)\
**Post date:** [April 23, 2024, 5:01pm UTC](https://community.netdata.cloud/t/troubleshooting-useless-misleading-nginx-number-of-seconds-since-the-last-successful-data-collection-alerts/5377/3 "2024-04-23T17:01:47Z")

</div>

Forgive me if I did not provide enough context. We have a Slack integration:

[Escalated to Critical, NGINX = 1213 seconds ago, on server.host.name]  
number of seconds since the last successful data collection

**Alert:**  
NGINX

**Chart:**  
nginx\_local.requests

**Context:**  
nginx.requests

* * *

Another one:

[Escalated to Critical, apache\_last\_collected\_secs = 1213 seconds ago, on server.host.name](https://app.netdata.cloud/spaces/redacted/rooms/all-nodes/alerts/apache_local.requests.apache_last_collected_secs:::0d6ce34d-4441-4f30-90bc-cc1dfc470c2a?chart=apache_local.requests&alarm=apache_last_collected_secs&transition=0cd1c75a-b2b9-4a79-8e5b-be50b732dcdd)

number of seconds since the last successful data collection

**Alert:**  
apache\_last\_collected\_secs

**Chart:**  
apache\_local.requests

## **Context:** apache.requests

Based on what I’m seeing, there is an alarm that goes off at 1213 seconds on various servers for both NGINX and Apache.

If you need different information, please be more specific. Thank you.

---

<div class="post-metadata">

**Author:** ![Ryan\_F](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ryan_f/32/3403_2.png) [@Ryan\_F](https://community.netdata.cloud/u/Ryan_F)\
**Post date:** [April 23, 2024, 5:03pm UTC](https://community.netdata.cloud/t/troubleshooting-useless-misleading-nginx-number-of-seconds-since-the-last-successful-data-collection-alerts/5377/4 "2024-04-23T17:03:50Z")

</div>

Also, some more context: We made our own NGINX last collected alarm by copying Apache’s, and they’re alerting at the same time.

---

<div class="post-metadata">

**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\
**Post date:** [April 24, 2024, 11:45am UTC](https://community.netdata.cloud/t/troubleshooting-useless-misleading-nginx-number-of-seconds-since-the-last-successful-data-collection-alerts/5377/5 "2024-04-24T11:45:05Z")

</div>

Are you using parent/child setup or standalone instances?

The reason for this alarm may be:

- nginx collector tries to gather metrics and keeps failing (e.g. nginx is not running or not reachable for some reason)
- collector stopped (exited) for some reason - in this case you shouldn’t see `go.d.plugin` in `ps faxu | grep netdata` output.

Do you see Nginx/Apache charts being updated while the alarm is triggered?

---

<div class="post-metadata">

**Author:** ![Ryan\_F](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ryan_f/32/3403_2.png) [@Ryan\_F](https://community.netdata.cloud/u/Ryan_F)\
**Post date:** [April 30, 2024, 4:58pm UTC](https://community.netdata.cloud/t/troubleshooting-useless-misleading-nginx-number-of-seconds-since-the-last-successful-data-collection-alerts/5377/6 "2024-04-30T16:58:43Z")

</div>

No, NGINX and Apache charts are not updated during these alarm triggers. However they seem to have stopped as suddenly as they started.

We’re using a parent/child instance of Netdata.

---

<div class="post-metadata">

**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\
**Post date:** [May 1, 2024, 8:27am UTC](https://community.netdata.cloud/t/troubleshooting-useless-misleading-nginx-number-of-seconds-since-the-last-successful-data-collection-alerts/5377/7 "2024-05-01T08:27:47Z")

</div>

Then the alarm is not useless. It indicates that the data collection stopped for some reason. Did you check the logs when this happened? Checking logs when something is not working is usually a good thing to do. This is how to [get logs since the last time Netdata was started on a systemd system](https://github.com/netdata/netdata/tree/master/src/libnetdata/log#using-journalctl-to-query-netdata-logs). You can send me your logs to `ilya@netdata.cloud` and I will take a look.

> It indicates that the data collection stopped for some reason.

And share the `ps faxu | grep netdata` output when the alarm is active.