Whats the suggested way of licensing a test/development environment?

[gebr]

Whats the suggested method to maintain a test/development environment in parallel to his production environment if the developer licence does no longer support clustering/search head clusters?

Deploying updates without testing them excessivly in our test environment is an absolute no-go.

[thellmann]

There are two types of developer licenses that can be used for non-production development and testing use cases:

50GB Personalized Dev/Test licenses are available to users associated with accounts with a paid Splunk Enterprise or Splunk Cloud license of any size and can be requested here: https://splunk.com/dev-test . These licenses do not allow clustering, among other restrictions.

10GB Developer licenses are available to everyone and can be requested using this form: https://dev.splunk.com/enterprise/dev_license . These licenses have a lower ingest volume, but have fewer feature restrictions.

[Anonymous]

Hi
I am using a DEV licens and I am also using it as a dev before going into production.
I am using SH-Cluster, and mine is working.
When did this stop?
In the readme faq, it only says limited usage and.

• Support for one authenticated account
• Single node
• No clustering

- No distributed search

Source: https://www.splunk.com/en_us/resources/personalized-dev-test-licenses/faq.html

We are using our DEV licens to test new apps agains our DEV Cluster.
Before making changes in Production.
Wil the support for clustering in DEV end?

[adonio]

use your dev as a license slave to your prod license master
carve a small license pool and call it ... lets say: "dev"
https://docs.splunk.com/Documentation/Splunk/8.0.0/Admin/Configurealicenseslave
https://docs.splunk.com/Documentation/Splunk/8.0.0/Admin/Createalicensepool

hope it helps