1/10/2024 0 Comments Splunk .conf 2017 mobile app.![]() When you next push the bundle, the app will be deleted from each peer. To delete an app that you previously distributed to the peers, remove its directory from the configuration bundle.For example, to distribute "appBestEver" to the peer nodes, place a copy of that app in its own subdirectory: $SPLUNK_HOME/etc/manager-apps/appBestEver. They provide a way to distribute any app to the peer nodes. The /_cluster/local subdirectory is where you can put new or edited configuration files that you want to distribute to the peers.This peer-specific default nf has a higher precedence than the standard default nf, located under $SPLUNK_HOME/etc/system/default. Do not add any files to this directory and do not change any files in it. The /_cluster/default subdirectory contains a default version of nf.The /_cluster directory is a special location for configuration files that need to be distributed across all peers:. ![]() This issue is discussed in detail elsewhere in this topic. If you choose to do so, substitute master-apps for all references to manager-apps in this manual. Although master-apps is deprecated, you can continue to use it, rather than switching to manager-apps. Starting with 9.0, a new directory called manager-apps was added to the cluster manager as a replacement for master-apps. Prior to Splunk Enterprise version 9.0, the cluster manager used the master-apps directory as the configuration bundle repository. They are always distributed as a group to all the peers. The set of files under that directory constitute the configuration bundle. On the manager, the configuration bundle resides under the $SPLUNK_HOME/etc/manager-apps directory. The configuration bundle consists of the set of files and apps common to all peer nodes. To distribute new or edited configuration files or apps across all the peers, you add the files to the configuration bundle on the manager node and tell the manager to distribute the files to the peers. The process used to distribute the configuration bundle is known as the configuration bundle method. The set of configuration files and apps common to all peers, which is managed from the manager node and distributed to the peers in a single operation, is called the configuration bundle. Since apps usually include versions of those key files, you should also maintain a common set of apps across all peers. Other configuration files can also be identical, depending on the needs of your system. In brief, the configuration files that must be identical in most circumstances are nf, nf, and nf. ![]() That topic details exactly which files must be identical across all peers. The process also runs automatically when a peer joins the cluster.įor information on peer configuration files, see Manage common configurations across all peers. You must manually invoke this process to distribute and update common files, including apps, to the peer nodes. ![]() The peer update process described in this topic ensures that all peer nodes share a common set of key configuration files. Update common peer configurations and apps ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |