# Configuring Axon in Turium

* [Compute Configuration](#compute-configuration)
* [Axon Configuration](#pipeline-configuration)
* [Engine Configuration](#engine-configuration)
* [Resources](#resources)
* [Axon Alerts](#pipeline-alerts)

Once you have deployed an axon, the following aspects can be configured: 

### **Compute Configuration** <a href="#compute-configuration" id="compute-configuration"></a>

You can modify the compute profile used to execute this axon. For instance, you might want to run the axon against an existing cluster instead of the default cluster.

***

### **Axon Configuration** <a href="#pipeline-configuration" id="pipeline-configuration"></a>

For each axon, the Instrumentation feature can be enabled or disabled. By default, Instrumentation is activated. If Instrumentation is enabled, running the axon will generate metrics for each node. The metrics for the source, transformation, and sink nodes slightly differ and include:

* Records out
* Records in
* Total number of errors
* Records out per second
* Min process time (one record)
* Max process time (one record)
* Standard deviation
* Average processing time

These metrics are displayed on the Metrics tab for each node in an axon. Unless the environment is resource-constrained, it is advised to always keep the Instrumentation setting on.

For streaming axons, the Batch interval for streaming data can also be set.

***

### **Engine Configuration** <a href="#engine-configuration" id="engine-configuration"></a>

For each axon, Spark or MapReduce can be selected as the execution engine, with Spark being the default option. Additional engine configurations can be added through custom configurations, which typically apply to Spark more frequently than to MapReduce.

***

### **Resources** <a href="#resources" id="resources"></a>

You can designate the memory and the number of CPUs for the driver and executor. The driver manages the Spark job while the executor handles data processing.

***

### **Axon Alerts** <a href="#pipeline-alerts" id="pipeline-alerts"></a>

After the axon execution concludes, you can set up Turium to dispatch alerts and initiate post-processing tasks. While designing the axon, axon alerts can be created. Once the axon is deployed, these alerts can be viewed, but no additional alerts can be added or existing ones edited. You can select the action to be performed by Turium upon the completion of an axon run, such as:

* Send email
* Execute a database query
* Create a marker file
* Make an HTTP call
* Run a MySQL query

You can choose to send an alert or trigger a post-processing task based on the run status. It is also possible to create custom nodes to perform specific tasks. Various open-source nodes can be added as an axon alert as well.

***

<br>


---

# Agent Instructions: 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:

```
GET https://docs.turium.ai/home/algoreus/turium-connector-documentation/turium-fabriq-overview/how-to-guides/axons-pipeline-user-guide/configuring-axon-in-turium.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.