Skip to content

Commit 0421398

Browse files
authored
Merge pull request #178326 from johnkemnetz/master
add limitations doc
2 parents c25dc41 + 9985806 commit 0421398

File tree

2 files changed

+40
-0
lines changed

2 files changed

+40
-0
lines changed

articles/chaos-studio/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,8 @@
4444
href: chaos-studio-fault-library.md
4545
- name: Fault providers
4646
href: chaos-studio-fault-providers.md
47+
- name: Preview limitations and known issues
48+
href: chaos-studio-limitations.md
4749
- name: Service limits
4850
href: chaos-studio-service-limits.md
4951
- name: REST API documentation
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
title: Azure Chaos Studio limitations and known issues
3+
description: Understand current limitations and known issues when using Azure Chaos Studio.
4+
services: chaos-studio
5+
author: johnkemnetz
6+
ms.topic: overview
7+
ms.date: 11/02/2021
8+
ms.author: johnkem
9+
ms.service: chaos-studio
10+
---
11+
12+
# Azure Chaos Studio Preview Limitations and Known Issues
13+
14+
During the public preview of Azure Chaos Studio, there are a few limitations and known issues that the team is aware of and working to resolve.
15+
16+
## Limitations
17+
18+
* For agent-based faults, the machine must have access to the following **HTTPS endpoints**:
19+
* http://agentcommunicationservice-frontdoor-canary.trafficmanager.net
20+
* If sending telemetry data to Application Insights, the IPs [in this document](../azure-monitor/app/ip-addresses.md) are also required.
21+
* If running an experiment that makes use of the Chaos Agent, the VM must run one of the following **operating systems**:
22+
* Windows Server 2019, Windows Server 2016, Windows Server 2012, and Windows Server 2012 R2
23+
* Redhat Enterprise Linux 8.2, SUSE Enterprise Linux 15 SP2, CentOS 8.2, Debian 10 Buster (with unzip installation required), Oracle Linux 7.8 Ubuntu Server 16.04 LTS, and Ubuntu Server 18.04 LTS
24+
* The Chaos Agent is not tested against custom Linux distributions, hardened Linux distributions (for example, FIPS or SELinux)
25+
* The Chaos Studio portal experience has only been tested on the following browsers:
26+
* **Windows:** Microsoft Edge, Google Chrome, Firefox
27+
* **MacOS:** Safari, Google Chrome, Firefox
28+
29+
## Known issues
30+
* Onboarding a target in the Azure portal may fail if you navigate away from the Targets view before onboarding completes.
31+
* When creating an experiment, after clicking **Review + create** there is a delay before the created experiment appears in the experiment list and users must refresh to see the experiment in the list.
32+
* When picking target resources for an agent-based fault in the experiment designer, it is possible to select virtual machines or virtual machine scale sets with an operating system not supported by the fault selected.
33+
34+
35+
## Next steps
36+
Get started creating and running chaos experiments to improve application resilience with Chaos Studio using the links below.
37+
- [Create and run your first experiment](chaos-studio-tutorial-service-direct.md)
38+
- [Learn more about chaos engineering](chaos-studio-chaos-engineering-overview.md)

0 commit comments

Comments
 (0)