Installation

Deploy Splunk with a different context

vikaskulkarni
Observer

Hi All,

I am trying to deploy Splunk in a different context.

By default when I run this command

/opt/splunk/bin/splunk start --accept-license

It starts the web with "/" as a deployment web context and I can access it by http://localhost:8000/

Now, if I would like to access Splunk like this

http://localhost:8000/splunk-local, so that all the redirect URLs would look like this

http://localhost:8000/splunk-local/en-US/app/launcher/home, http://localhost:8000/splunk-local/en-US/account/login?return_to=%2Fen-US%2Fapp%2Flauncher%2Fhome

Reason for asking this question: In the Kubernetes environment, it's a bit challenging to configure Networks for applications using the default "/" as a context

Thanks

Vikas

@jho-splunk @daniel333 @48tfhd86gv @gcusello @dstromberg 

Labels (1)
0 Karma

vikaskulkarni
Observer

Hey, after posting the question, I was doing some more digging and found that if I override root_endpoint value in $SPLUNK_HOME/etc/system/default/web.conf, it works

# Top level name for the site
root_endpoint = /splunk-local
 
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!

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...