Hi to all,
I have three machines: 1 deployment-server, 1 SH/Indexer and 1 forwarder. Looking at "monitoringconsole-panoramics" on deployment-server, i don't see the correct configuration (is a...
On a Windows Server when I go to Settings \ MonitoringConsole and launch it, there is a Menu item called: Forwarders: Instance which appears not to be configured and when I try to run setup I get t...
...eployment apps pushed down to these forwarders as follows:
App1 – indexer_config: Sets outputs.conf to point to indexer and defines clientCert and sslRootCAPath cert.
App2 – Splunk_TA_Windows: This App configure...
hi,
we have few heavy forwarders which are used for intermediate forwarding to Indexers. In DMC (Distributed management console), we have got these forwarders correctly in the "Forwarders" S...
I already configured my Splunk universal forwarder to send data to my Splunk cloud trial and I am getting this error.
10-24-2017 21:22:27.533 -0500 WARN TcpOutputProc - Tcpout Processor: The T...
...locked for blocked_seconds=3100. This can stall the data flow towards indexing and other network outputs. Review the receiving system's health in the Splunk MonitoringConsole. It is probably not a...
I need details about what to check before I upgrade so I know if my deployment is ready to upgrade. What do I monitor, and how do I benchmark system health before the upgrade?
Hi,
I didn't find detailed info, how to connect Universal Forwarders to MonitoringConsole.
In our organization there is no deployment server, but we do want to monitor Splunk UF/HF with monitoring...
I need details about what to validate after the upgrade so I know it was successful. How can I tell that everything got upgraded correctly, and that the system is healthy and ready to go?