> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/resilience-testing/chaos-engineering/chaos-experiments/probe.md).

# Probes

Probes are validation mechanisms that continuously monitor and verify the health and behavior of your system throughout chaos experiments. They act as automated checkpoints that help you:

* **Validate system resilience** - Verify that your applications and infrastructure maintain expected behavior under failure conditions
* **Define success criteria** - Set clear, measurable conditions that determine whether an experiment passes or fails
* **Collect evidence** - Gather real-time data about system state, performance metrics, and application health
* **Automate validation** - Replace manual observation with automated checks that run at specific points during experiments

Probes can query various data sources including HTTP endpoints, command outputs, Kubernetes resources, and APM systems to provide comprehensive visibility into your system's resilience.

{% hint style="info" %}
**IMPORTANT: PROBE SCOPE DIFFERENCES**

* **Old Chaos Studio**: Probes are scoped to individual faults and execute only during fault injection
* **New Chaos Studio**: Probes operate along the entire experiment lifecycle and can be configured to run before, during, and after the complete experiment execution
  {% endhint %}

### Probe Verification <a href="#probe-verification" id="probe-verification"></a>

Probes can be marked as **Verified** to ensure only tested and approved probes are used in production experiments. This governance feature helps teams:

* **Maintain quality standards** - Only allow probes that have been validated and approved by your team
* **Prevent misconfigurations** - Reduce the risk of using untested or incorrectly configured probes in critical experiments
* **Enforce compliance** - Use with [ChaosGuard](/resilience-testing/chaos-engineering/use-chaos-engineering/governance/governance-in-execution/govern-run.md) policies to mandate that only verified probes can be executed

#### How to Mark a Probe as Verified <a href="#how-to-mark-a-probe-as-verified" id="how-to-mark-a-probe-as-verified"></a>

1. Navigate to the **Probes & Actions** section in the Chaos Engineering module
2. Locate the probe you want to verify
3. Click on the three-dot menu (⋮) next to the probe
4. Select **Mark as Verified**

   ![Mark as Verified](/files/bo2PWKUzBPCcTKKbDsYj)

Once marked as verified, the probe will display a green checkmark (✓) in the **Verification Status** column. You can then configure ChaosGuard conditions to allow only verified probes in your experiments, adding an extra layer of safety and governance.

{% hint style="info" %}
Combine probe verification with ChaosGuard policies to create a robust governance framework that ensures only approved, tested probes are used in your chaos experiments.
{% endhint %}

### Probe Types <a href="#probe-types" id="probe-types"></a>

Select the probe type you want to learn more about:

{% @harness-package-selector/package-selector platforms="%5B%7B%22label%22%3A%22HTTP%20Probe%22%2C%22slug%22%3A%22http-probe%22%2C%22path%22%3A%22chaos-engineering%2Fguides%2Fprobe%2Fhttp-probe-probe%22%7D%2C%7B%22label%22%3A%22Command%20Probe%22%2C%22slug%22%3A%22command-probe%22%2C%22path%22%3A%22chaos-engineering%2Fguides%2Fprobe%2Fcommand-probe-probe%22%7D%2C%7B%22label%22%3A%22Prometheus%20Probe%22%2C%22slug%22%3A%22prometheus-probe%22%2C%22path%22%3A%22chaos-engineering%2Fguides%2Fprobe%2Fprometheus-probe-probe%22%7D%2C%7B%22label%22%3A%22K8S%20Probe%22%2C%22slug%22%3A%22k8s-probe%22%2C%22path%22%3A%22chaos-engineering%2Fguides%2Fprobe%2Fk8s-probe-probe%22%7D%2C%7B%22label%22%3A%22Datadog%20Probe%22%2C%22slug%22%3A%22datadog-probe%22%2C%22path%22%3A%22chaos-engineering%2Fguides%2Fprobe%2Fdatadog-probe-probe%22%7D%2C%7B%22label%22%3A%22Dynatrace%20Probe%22%2C%22slug%22%3A%22dynatrace-probe%22%2C%22path%22%3A%22chaos-engineering%2Fguides%2Fprobe%2Fdynatrace-probe-probe%22%7D%2C%7B%22label%22%3A%22SLO%20Probe%22%2C%22slug%22%3A%22slo-probe%22%2C%22path%22%3A%22chaos-engineering%2Fguides%2Fprobe%2Fslo-probe-probe%22%7D%2C%7B%22label%22%3A%22APM%20Probe%22%2C%22slug%22%3A%22apm-probe%22%2C%22path%22%3A%22chaos-engineering%2Fguides%2Fprobe%2Fapm-probe-probe%22%7D%2C%7B%22label%22%3A%22Container%20Probe%22%2C%22slug%22%3A%22container-probe%22%2C%22path%22%3A%22chaos-engineering%2Fguides%2Fprobe%2Fcontainer-probe-probe%22%7D%5D" %}

### Built-in Probe Templates <a href="#built-in-probe-templates" id="built-in-probe-templates"></a>

Harness provides pre-built Command Probe templates to help you quickly validate common scenarios in your chaos experiments. These templates are ready to use and can be customized to fit your specific requirements.

{% hint style="info" %}
Currently, built-in templates are available for **Command Probes** targeting **Kubernetes** infrastructure. Templates for other probe types and platforms will be added in future releases.
{% endhint %}

import ChaosFaults from '@site/src/components/ChaosEngineering/ChaosFaults'; import { probeTemplateCategories } from '../content/probes/probe-templates';

### Next Steps <a href="#next-steps" id="next-steps"></a>

* [Create Chaos Experiments](/resilience-testing/chaos-engineering/use-chaos-engineering/experiments.md) - Build experiments with probes for validation