> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/logs-were-not-collected-from-a-data-source-for-an-abnormally-long-time.md).
# Logs were not collected from a data source for an abnormally long time
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 1 Day |
| Deduplication Period | 6 Hours |
| Required Data | Health Monitoring Data |
| ATT\&CK Tactic | Impact (TA0040) |
| ATT\&CK Technique | Network Denial of Service (T1498), Service Stop (T1489) |
| Severity | Low |
### Description
Logs were not collected from a data source for an abnormally long time.
### Attacker's Goals
N/A.
### Investigative actions
N/A.
### Variations
Logs were not collected from a Windows Event Collector (WEC) for an abnormally long time
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------- |
| ATT\&CK Tactic | Impact (TA0040) |
| ATT\&CK Technique | Network Denial of Service (T1498), Service Stop (T1489) |
| Severity | Low |
**Description**
Logs were not collected from a data source for an abnormally long time.
**Attacker's Goals**
N/A.
**Investigative actions**
N/A.
Logs were not collected from a Microsoft Windows XDR Collector (XDRC) for an abnormally long time
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------- |
| ATT\&CK Tactic | Impact (TA0040) |
| ATT\&CK Technique | Network Denial of Service (T1498), Service Stop (T1489) |
| Severity | Low |
**Description**
Logs were not collected from a data source for an abnormally long time.
**Attacker's Goals**
N/A.
**Investigative actions**
N/A.
Logs were not collected from a data source for an abnormally long time, which indicates a significant stop
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------- |
| ATT\&CK Tactic | Impact (TA0040) |
| ATT\&CK Technique | Network Denial of Service (T1498), Service Stop (T1489) |
| Severity | Medium |
**Description**
Logs were not collected from a data source for an abnormally long time.
**Attacker's Goals**
N/A.
**Investigative actions**
N/A.
Logs were not collected from a data source for an abnormally long time, despite a stable and consistent data stream until recently
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------- |
| ATT\&CK Tactic | Impact (TA0040) |
| ATT\&CK Technique | Network Denial of Service (T1498), Service Stop (T1489) |
| Severity | Medium |
**Description**
Logs were not collected from a data source for an abnormally long time.
**Attacker's Goals**
N/A.
**Investigative actions**
N/A.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/logs-were-not-collected-from-a-data-source-for-an-abnormally-long-time.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.