# Run Snowplow Micro through Console
> Run Snowplow Micro through Snowplow Console to validate and debug tracking implementations. Send events to the collector endpoint and view results through the dashboard.
> Source: https://docs.snowplow.io/docs/testing/snowplow-micro/console/
> Documentation index: https://docs.snowplow.io/llms.txt

Snowplow Micro is fully integrated in Snowplow Console:

- You can deploy one or more Micro-based **development environments**
- Each environment is automatically connected to your development [data structures](/docs/event-studio/data-structures/)
- You can manage [enrichments](/docs/pipeline/enrichments/available-enrichments/) the same way as for regular pipelines, and copy enrichment configuration from a development environment to a pipeline

> **Tip:** Using a development environment is a great way to test your changes before applying them to a real pipeline.

## Setup

To create a development environment, navigate to **Settings > Workspaces**, select your workspace, scroll to the **Development environments** section and click **Create environment**.

> **Note: Permissions**
>
> You will need _Edit environments_ permissions to do this.

You can add multiple environments, or create and delete them as you see necessary. For example, it might be convenient to create separate environments for different teams testing different code in parallel.

Under the hood, an instance of Snowplow Micro will be deployed in your cloud account along with a database to store events. (This account is managed by you, in the case of Private Managed Cloud, or by Snowplow otherwise.)

## Usage

Once your development environment is ready, you can access it from the **Pipelines** section in the Console sidebar.

Select your environment and you will see the Collector endpoint URL you can use in your tracking code to send events to this environment.

Events will be stored for a (rolling) 7 day period.

To view events in the [Micro dashboard](/docs/testing/snowplow-micro/ui/), select your environment and then click **Open dashboard**.

> **Warning: Production data**
>
> Do not send production data to development environments. Anyone with the _View environments_ permission can access the dashboard and see the events. Also, development environments are not configured to withstand high volumes of events.

To enable or disable enrichments and edit their configurations, select the **Enrichments** tab. The process is the same as for regular pipelines. We highly recommend testing enrichments in a development environment before deploying them to production.

## Validate event specifications

Development environments validate incoming events the same way [event specification validation](/docs/event-studio/tracking-plans/event-specification-validation/) does in a pipeline. The environment checks each event against the version that its `event_specification` entity declares. An event that declares a published version validates against that version even when a draft exists. Unlike pipelines, development environments also load the draft of each [event specification](/docs/event-studio/tracking-plans/event-specifications/), so you can test a draft without publishing the specification.

Edit the specification in Console, send a test event, and inspect the result in the [Micro dashboard](/docs/testing/snowplow-micro/ui/). Events that fail validation carry an `event_specification_validation` entity describing each error. The environment picks up specification changes within a few minutes.

The environment infers a specification for events that arrive without an `event_specification` entity. Inference considers one version of each specification: the draft when there is one, and the highest published version otherwise. See [event specification inference](/docs/event-studio/tracking-plans/event-specification-inference/) for how the pipeline matches an event.