Splunk Dev

Finding the Splunk Cloud version of Indexers & Cluster Master

anandhalagaras1
Contributor

We have deployed Splunk Cloud in our environment. So just want to know what version we are running our Indexers, Cluster master, License master etc.

Since in Search head we can check the information in "Support & Services" in the right corner and click About. In which it will display the version information of the search head.

But we cant able to find the Indexer and Cluster master Splunk version details since it is hosted in Cloud. So do we have any query to find the information or is there any page where i can check those information.

It will be really helpful if you can help on this.

Tags (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

It's a safe bet that all of your Splunk Cloud instances are the same version as your search head.

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

anandhalagaras1
Contributor

@richgalloway

Thank you for your prompt response.

But can i able to visualize the Splunk version information (Indexers & Cluster master) anywhere in the Search head with a help of a search query?

Something like that.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Try this query for the indexers. I believe Splunk Cloud customers do not have access to the Cluster Master.

| rest /services/server/info | table host splunk_server startup_time version server_roles
---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Splunk at Cisco Live 2025: Learning, Innovation, and a Little Bit of Mr. Brightside

Pack your bags (and maybe your dancing shoes)—Cisco Live is heading to San Diego, June 8–12, 2025, and Splunk ...

Splunk App Dev Community Updates – What’s New and What’s Next

Welcome to your go-to roundup of everything happening in the Splunk App Dev Community! Whether you're building ...

The Latest Cisco Integrations With Splunk Platform!

Join us for an exciting tech talk where we’ll explore the latest integrations in Cisco + Splunk! We’ve ...