Advanced test configurations 🔗

サイトやアプリケーションへの多様なトラフィックをシミュレートするには、さまざまな設定オプションを使用して、各テストをカスタマイズします。

テストの命名規則 🔗

テストやアラートに有益な名前を選ぶことは、コンテンツの整理に役立ちます。以下にガイドラインを示します：

グループ名、アプリケーション名、ブランド名、チーム名など、テスト名の前にカテゴリを付けて、検索を簡素化します。例えば、これら2つのブラウザテストは [ButtercupGames] で始まります。
ワークフロー、プロセス、パフォーマンス、データソースなど、テストの目的に関する説明を追加します。

This image shows two browser tests with the prefix [ButtercupGames].

このページは 2025年03月03日に最終更新されました。

Was this topic useful?

Did you know that you can edit this page? Learn how!

Was this documentation topic helpful?

Enter your email address if you would like someone from the documentation team to reply to your question or suggestion.

Please provide your comments here. Ask a question or make a suggestion.

Comment should have a minimum of 5 characters and a maximum of 1,000 characters.

Feedback submitted, thank you! We resolve documentation feedback based on the severity of the issue reported, as well as an assessment of the potential number of customers who might be affected.

If you have a question about using Splunk software, we encourage you to check Splunk Answers or Splunk community Slack to see if similar questions have been answered, or to post your question for others to answer. If you have an active support entitlement and believe that your situation is caused by a product defect, file a support case in the Support portal https://login.splunk.com/page/sso_redirect?type=portal.

We are currently moving to a new documentation site. Expect a delay in responding to your feedback and applying any updates based on your feedback. Thank you for your patience and understanding while we work to bring you an improved documentation experience!