Deployment Architecture

query to check fixup , SF, RF and data is searchable in splunk

Praz_123
Communicator

Is there is any query to check like if there is any fixup pending and also it shows SF , RF and data is searchable  in the cluster master .

We can check in cluster master U.I but without going there is there anywhere this log are store so that we can fetch.

I need to created a query which shows the status of SF, RF and searchable in Cluster Master also if there are any fixup pending.

Labels (1)
0 Karma

splunkmarroko
Engager

try this:
| rest/services/data/indexes
| table  title searchFactor replicationFactor
 and to check if data is searchable :
|metadata type=source
|search source IN(your_datasource)

0 Karma

livehybrid
SplunkTrust
SplunkTrust

Hi @Praz_123 

You could try a rest call:

| rest /services/cluster/manager/health

This returns a number of interesting fields around SF/RF.

eturned values

Name Datatype Description

all_data_is_searchableBooleanIndicates if all data in the cluster is searchable.
all_peers_are_upBooleanIndicate if all peers are strictly in the Up status.
cm_version_is_compatibleBooleanIndicates if any cluster peers are running a Splunk Enterprise version greater than or equal to the cluster manager's version.
multisiteBooleanIndicates if multisite is enabled.
no_fixups_in_progressBooleanIndicates if there does not exist buckets with bucket state NonStreamingTarget, or bucket search states PendingSearchable or SearchablePendingMask.
pre_flight_checkBooleanIndicates if the health check prior to a rolling upgrade was successful. This value is true only if the cluster passed all health checks.
replication_factor_metBooleanOnly valid for mode=manager and multisite=false. Indicates whether the replication factor is met. If true, the cluster has at least replication_factor number of raw data copies in the cluster.
search_factor_metBooleanOnly valid for mode=manager and multisite=false. Indicates whether the search factor is met. If true, the cluster has at least search_factor number of raw data copies in the cluster.
site_replication_factor_metBooleanOnly valid for mode=manager and multisite=true. Indicates whether the site replication factor is met. If true, the cluster has at least replication_factor number of raw data copies in the cluster.
site_search_factor_metBooleanOnly valid for mode=manager and multisite=true. Indicates whether the site search factor is met. If true, the cluster has at least site_search_factor number of raw data copies in the cluster.
splunk_version_peer_countStringLists the number of cluster peers running each Splunk Enterprise version.

Check out the docs at https://docs.splunk.com/Documentation/Splunk/9.4.1/RESTREF/RESTcluster#cluster.2Fmanager.2Fhealth for more info on all the fields.

You could also check:

| rest /services/cluster/manager/info
active_bundleProvides information about the active bundle for this manager.
bundle_creation_time_on_managerThe time, in epoch seconds, when the bundle was created on the manager.
bundle_validation_errors_on_managerA list of bundle validation errors.
bundle_validation_in_progressIndicates if bundle validation is in progress.
bundle_validation_on_manager_succeededIndicates whether the manager succeeded validating bundles.
data_safety_buckets_to_fixLists the buckets to fix for the completion of data safety.
gen_commit_buckets_to_fixThe buckets to be fixed before the next generation can be committed.
indexing_ready_flagIndicates if the cluster is ready for indexing.
initialized_flagIndicates if the cluster is initialized.
labelThe name for the manager. Displayed in the Splunk Web manager page.
latest_bundleThe most recent information reflecting any changes made to the manager-apps configuration bundle.

In steady state, this is equal to active_bundle. If it is not equal, then pushing the latest bundle to all peers is in process (or needs to be started).

maintenance_modeIndicates if the cluster is in maintenance mode.
reload_bundle_issuedIndicates if the bundle issued is being reloaded.
rep_count_buckets_to_fixNumber of buckets to fix on peers.
rolling_restart_flagIndicates whether the manager is restarting the peers in a cluster.
search_count_buckets_to_fixNumber of buckets to fix to satisfy the search count.
service_ready_flagIndicates whether the manager is ready to begin servicing, based on whether it is initialized.
start_timeTimestamp corresponding to the creation of the manager.

 

If you want specific fix-up info check out https://docs.splunk.com/Documentation/Splunk/9.4.1/RESTREF/RESTcluster#cluster.2Fmanager.2Ffixup

 

🌟Did this answer help you? If so, please consider:

  • Adding kudos to show it was useful
  • Marking it as the solution if it resolved your issue
  • Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing.

0 Karma

Praz_123
Communicator

@livehybrid  I ran the 

| rest /services/cluster/manager/health


But while CM was down at that time also am getting value 1 but it should show 0 .

As I need to create a Alert for this but am not getting the correct output 

0 Karma
Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

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

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...