Skip to content

Commit b9a6907

Browse files
authored
Merge pull request #2501 from splunk/adasplunk-O11YDOCS-6760
[6760] Update wording on global variables
2 parents 5aa2208 + c5097cc commit b9a6907

File tree

1 file changed

+4
-8
lines changed

1 file changed

+4
-8
lines changed

synthetics/test-config/global-variables.rst

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,24 +7,20 @@ Create and use global variables
77
.. meta::
88
:description: Define a variable that you can use in multiple browser and API tests in Splunk Synthetic Monitoring.
99

10-
Define a global variable once, and then you can use the variable across all of your browser and API tests.
10+
Define a global variable once, and then use it across all of your browser and API tests.
1111

1212

1313
How can you use a global variable?
1414
===================================
15-
Global variables are stored securely in Splunk Synthetic Monitoring, but the keys and values of all global variables in your account are visible to all users.
15+
Use global variables to store non-sensitive information for your browser and API tests. Splunk Synthetic Monitoring saves your global variables, but note that their values are visible to all users in your account.
1616

17-
To preserve your account's security, don't use production credentials, real credit card information, or other sensitive data in global variables for your tests. Instead, use placeholder credentials to test workflows that require you to enter information.
18-
19-
To use information such as login credentials, API keys, or other test data, you can permanently conceal the value of a global variable from all users of your account.
17+
To preserve your account's security, don't use global variables to store sensitive information such as login credentials, API keys, or credit card information. Instead, either use placeholder values or permanently conceal the global variables that contain sensitive information.
2018

2119
.. _concealed-gv:
2220

2321
What happens when you conceal a global variable?
2422
==================================================
25-
When you conceal a global variable, its value is permanently concealed from all users of the account. This lets you create and save variables such as test login credentials, API keys, and other sensitive information to use in browser and API tests.
26-
27-
To preserve security, the value of a concealed global variable is never revealed to any user of the account after it has been created and saved. The value is scrubbed from the Splunk Synthetic Monitoring UI, from test results, and from alert messages.
23+
When you conceal a global variable, Splunk Synthetic Monitoring permanently hides its value from all users of your account. Concealed values are never revealed; they are scrubbed from the Splunk Synthetic Monitoring UI, from test results, and from alert messages. However, if you send a concealed value to a test endpoint, that endpoint receives its unconcealed value.
2824

2925

3026
Create a global variable

0 commit comments

Comments
 (0)