All Apps and Add-ons

Installing Website Monitoring on Distributed Environment

sramiz
Path Finder

hello,

We have one searchhead and one indexer server running on separate VMs. wondering where should we install website monitoring application? any tip or advise is much appreciated.

regards,
SR

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

None of the above. See https://docs.splunk.com/Documentation/AddOns/released/Overview/Wheretoinstall . Apps that define inputs should be installed on a forwarder (heavy forwarder in your case). If you don't want to or can't create a HF, install the app on the indexer. Be aware that the input will affect the performance of the indexer.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

jwiedow
Communicator

@sramiz , you will actually want the Website Monitoring App installed on a Heavy Forwarder; as @richgalloway indicated, AND your searchhead. The app on the searchhead will provide the visualizations for the results coming out of your indexed data. You need to make sure that the permissions for Data Inputs is set so that noone is able to create a new web_ping input on your searchhead and you are managing those on your Heavy Forwarder.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

None of the above. See https://docs.splunk.com/Documentation/AddOns/released/Overview/Wheretoinstall . Apps that define inputs should be installed on a forwarder (heavy forwarder in your case). If you don't want to or can't create a HF, install the app on the indexer. Be aware that the input will affect the performance of the indexer.

---
If this reply helps you, Karma would be appreciated.

sramiz
Path Finder

thank you for clarification

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...