> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/reference-1/sql-commands/jobs/create-job/monitoring.md).

# Monitoring

Upsolver provides integration with popular reporting platforms to enable you to monitor your pipelines from a central dashboard. Using SQL syntax, you can create jobs to export monitoring data.  

#### Supported targets

* [Amazon CloudWatch](/content/reference-1/sql-commands/jobs/create-job/monitoring/amazon-cloudwatch.md)
* [Datadog](/content/reference-1/sql-commands/jobs/create-job/monitoring/datadog.md)
* [Dynatrace](/content/reference-1/sql-commands/jobs/create-job/monitoring/dynatrace.md)

## Syntax

```sql
CREATE JOB <job_identifier> 
      [ START_FROM = { NOW | BEGINNING | <timestamp> } ]
AS INSERT INTO [ CLOUDWATCH | DATADOG | DYNATRACE ] <connection_identifier>
      [ NAMESPACE = '<namespace>' ]
      [ MAP_COLUMNS_BY_NAME ]
SELECT ...
      [ tags ]
      <timestamp> AS time
```

**Jump to**

* [`MAP_COLUMNS_BY_NAME`](#map_columns_by_name)
* [`NAMESPACE`](#namespace)
* [`START_FROM`](#start_from)

#### `MAP_COLUMNS_BY_NAME`

Maps columns from the `SELECT` statement to the table by the names of the columns in the query. For more information see [`MAP_COLUMS_BY_NAME`](/content/reference-1/sql-commands/jobs/create-job/transformation/insert/map_columns_by_name.md).

#### `NAMESPACE`

Type: `text`

(Optional) The target namespace for your Upsolver metrics in Amazon CloudWatch. If the namespace does not already exist, Upsolver creates it for you.

Note: if you are using the `NAMESPACE` option, ensure this is defined immediately after the connection identifier.

#### `START_FROM`

Values: `{ NOW | BEGINNING | <timestamp> }`

Default: `NOW`

(Optional) Configures the time to start sending data to the target.

***

## Query structure

Your job should include the following:

* At least one metric
* The time when the metric data was captured
* Optionally, you can include tags, which are metadata strings, e.g. the name of the cluster or job&#x20;

{% hint style="success" %}
**Learn more**

Follow the guide on [How to Export Metrics to a Third-Party System](/content/how-to-guides-1/jobs/job-monitoring/export-metrics-to-a-third-party-system.md) for a walk through on creating your monitoring job.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://upsolver.gitbook.io/content/reference-1/sql-commands/jobs/create-job/monitoring.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.