Deployment Architecture

Path on server for the url: http(s)://Search_Head:8000

ishaanshekhar
Communicator

I have a SHC of 4 SHs with a h/w LB upfront.

There needs to be a health_check_api.html file in the server so that the LB can use that to check whether the SH is up or not.

My question is, what is the path in the server when we hit the URL http(s)://SearchHead>:8000 so that I could keep my api file health_check_api.html file in that location?

Thanks,
Ishaan

0 Karma
1 Solution

sideview
SplunkTrust
SplunkTrust

You have a couple options.

If you have an app called myapp,
then

1) The newer way (6.0+ or possibly back to 5.0), putting it in
$SPLUNK_HOME/etc/apps/myapp/static

will give you a URL of:
http://searchhead:8000/en-US/splunkd/__raw/servicesNS/admin/myapp/static/health_check_api.html

2) Or the older way, you can put it in
$SPLUNK_HOME/etc/apps/myapp/appserver/static
and this will give you a URL of:

http://searchhead:8000/en-US/static/app/sideview_utils/health_check_api.html

It's possible that someday Splunk might remove the legacy appserver/static path so maybe #1 is better, but this is just speculation.

And as you might guess from #1, there is an equivalent URL on Splunkd's port to the same file
https://searchhead:8089/servicesNS/admin/cisco_cdr/static/appIcon.png
(note the port is the 8089 port here and not the 8000 port)

but of course you would need to pass HTTP auth on that request and that probably isn't feasible.

View solution in original post

sideview
SplunkTrust
SplunkTrust

You have a couple options.

If you have an app called myapp,
then

1) The newer way (6.0+ or possibly back to 5.0), putting it in
$SPLUNK_HOME/etc/apps/myapp/static

will give you a URL of:
http://searchhead:8000/en-US/splunkd/__raw/servicesNS/admin/myapp/static/health_check_api.html

2) Or the older way, you can put it in
$SPLUNK_HOME/etc/apps/myapp/appserver/static
and this will give you a URL of:

http://searchhead:8000/en-US/static/app/sideview_utils/health_check_api.html

It's possible that someday Splunk might remove the legacy appserver/static path so maybe #1 is better, but this is just speculation.

And as you might guess from #1, there is an equivalent URL on Splunkd's port to the same file
https://searchhead:8089/servicesNS/admin/cisco_cdr/static/appIcon.png
(note the port is the 8089 port here and not the 8000 port)

but of course you would need to pass HTTP auth on that request and that probably isn't feasible.

Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) v3.54.0

The Splunk Threat Research Team (STRT) recently released Enterprise Security Content Update (ESCU) v3.54.0 and ...

Using Machine Learning for Hunting Security Threats

WATCH NOW Seeing the exponential hike in global cyber threat spectrum, organizations are now striving more for ...

New Learning Videos on Topics Most Requested by You! Plus This Month’s New Splunk ...

Splunk Lantern is a customer success center that provides advice from Splunk experts on valuable data ...