A " no data " message in NetFlow charts usually indicates that the flow collector service is not receiving or processing flow data. One of the primary troubleshooting steps recommended in the SolarWinds documentation is to restart the collector service. This resolves issues caused by service interruptions, memory leaks, or flow processing errors.
The documentation states:
" If NetFlow charts display ' no data, ' verify that the NetFlow collector service is running. Restart the collector service if necessary, as service interruptions can cause a lack of flow data display. " References:
Network Performance Monitor Administrator Guide, " Troubleshooting NetFlow No Data Issues " SolarWinds Success Center: " NetFlow Collector Service Troubleshooting "

According to the SolarWinds Log Analyzer Administrator Guide (Version 2024.1) , Log Analyzer provides several built-in or native log entry actions as part of its log-processing rules. The key native log entry actions include:
* Add a tag to the log entry : This action allows you to tag event logs for easier searching and filtering later.
* Continue rule processing but do not save : With this action, the log entry is not saved but rule processing continues.
* Halt further rule processing for the log entry : Selecting this action will immediately stop the processing of any more rules for the current log entry.
Sending an email notification is an alert action and not considered a native log entry action in the context of log processing rules.
Exact Extract from Official Guide:
" Key features in LA
* Apply tags to event logs
* Drop unwanted event logs in LA
* Filter and analyze event logs
* Filter and view event logs in live mode
* Filter entry details in LA
* Filter on log tags... " - (Log Analyzer Administrator Guide, Page 53-54) Additionally, the guide specifies under Create custom log-processing rules in LA that actions such as tagging, halting processing, and not saving are among the native processing actions.
References:
Log Analyzer Administrator Guide, Page 53-54
Section: Key features in LA
Section: Create custom log-processing rules in LA

NetPath probes require a supported Windows environment for deployment. According to the SolarWinds documentation, probes can be run from the Hybrid Cloud Observability (HCO) server itself, which must be a Windows server, or from any Windows client computer, including Windows 10. NetPath agents are not available for Linux or for network devices such as routers; the agent cannot be installed on Red Hat Linux or routers.
Reference:
Network Performance Monitor Administrator Guide, "Deploying NetPath Probes," NetPath Requirements: "NetPath probes can only be deployed on Windows computers or servers running supported Windows operating systems."