Deploying Splunk through the Linode Marketplace
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Splunk is a powerful log analyzer that can be used to obtain insight into your infrastructure. Splunk collects, monitors, analyzes, and visualizes data from database applications, web servers, cloud networks, and a variety of other sources.
Deploying the Splunk Marketplace App
The Linode Marketplace allows you to easily deploy software on a Linode using the Linode Cloud Manager.
Log in to the Cloud Manager and select the Marketplace link from the left navigation menu. This displays the Linode Compute Create page with the Marketplace tab pre-selected.
Under the Select App section, select the app you would like to deploy.
Fill out all required Options for the selected app as well as any desired Advanced Options (which are optional). See the Configuration Options section for details.
Complete the rest of the form as discussed within the Getting Started > Create a Linode.
Click the Create Linode button. Once the Linode has provisioned and has fully powered on, wait for the software installation to complete. If the Linode is powered off or restarted before this time, the software installation will likely fail. To determine if the installation has completed, open the Linode’s Lish console and wait for the system login prompt to appear.
Follow the instructions within the Getting Started After Deployment section.
Software installation should complete within 2-5 minutes after the Linode has finished provisioning.
Configuration Options
Splunk Options
You can configure your Splunk App by providing values for the following fields:
| Field | Description |
|---|---|
| Splunk Username | This will be the username you use to login the Splunk Dashboard. Required. |
| Splunk Password | This will be the password you use to login the Splunk Dashboard. Required. |
| The limited sudo user to be created for the Linode | The username for a new limited user account with sudo privileges. |
| The password for the limited sudo user | The password for the new limited user account. |
| The SSH Public Key that will be used to access the Linode | A public key belonging to the user that accesses the Linode. If you do not have an authentication key-pair, see the Securing Your Server guide for steps on creating one. |
| Disable root access over SSH | Disable root user access for the Linode server. |
| Your Linode API token | The Linode API v4 token is required to create a domain name system (DNS) record. See the Getting Started with the Linode API guide to learn how to generate an API token. |
| The domain for the Linode’s DNS record (Requires API token) | The hostname to assign to the Linode server. |
| The subdomain for the Linode’s DNS record (Requires API token) | The domain name to use when creating a DNS record for the Linode. |
| Admin email for the Splunk server | The email address to use for the Splunk instance’s admin user. |
General Options
For advice on filling out the remaining options on the Create a Linode form, see Getting Started > Create a Linode. That said, some options may be limited or recommended based on this Marketplace App:
- Supported distributions: Debian 10 and Ubuntu 20.04 LTS
- Recommended minimum plan: All plan types and sizes can be used.
Getting Started after Deployment
Access your Splunk App
Open a browser and navigate to your
Linode’s IP address and port 8000, for example, http://192.0.2.0:8000/. You will be presented a login field where you can enter the credentials you previously specified in the Splunk Username and Splunk Password fields when you deployed the app.
Now that you’ve accessed your dashboard, checkout the official Splunk documentation to learn how to further configure your instance.
NoteCurrently, Linode does not manage software and systems updates for Marketplace Apps. It is up to the user to perform routine maintenance on software deployed in this fashion.
More Information
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on