> For the complete documentation index, see [llms.txt](https://docs.akamas.io/akamas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/akamas-docs/3.6/integrating/integrating-telemetry-providers/spark-history-server-provider.md).
# Spark History Server provider
The **Spark History Server provider** collects metrics from a Spark History Server instance and makes them available to Akamas.
Prerequisites
This section provides the minimum requirements that you should match before using the Spark History Server telemetry provider.
### Supported versions
* Apache Spark 2.3
### Network requirements
* Spark History Server API must be reachable at the provided address and port (the default port is `18080`).
## Supported component types
* spark-application
You can check [Spark History Server provider metrics mapping](/akamas-docs/3.6/reference/optimization-packs/spark-pack.md) to see how component-types metrics are extracted by this provider.
## Akamas supported version
* Versions < 2.0.0 are compatible with Akamas until version 1.8.0
* Versions >= 2.0.0 are compatible with Akamas from version 1.9.0
## Workflow requirements
This section lists the workflow operators this provider depends on:
* [SparkSubmit Operator](/akamas-docs/3.6/reference/workflow-operators/sparksubmit-operator.md)
* [SparkSSHSubmit operator](/akamas-docs/3.6/reference/workflow-operators/sparksshsubmit-operator.md)
* [SparkLivy Operator](/akamas-docs/3.6/reference/workflow-operators/sparklivy-operator.md)
## Components configuration
Akamas uses components to identify specific elements of the system to be monitored and optimized. Your system might contain multiple components to model, for example, a Spark application and each host of the cluster. To point Akamas to the right component when extracting metrics you need to add a property called `sparkApplication` to your Spark Application component. The provider will only extract metrics for components for which this property has been specified.
```yaml
name: My Application
properties:
sparkApplication: "true"
```
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.akamas.io/akamas-docs/3.6/integrating/integrating-telemetry-providers/spark-history-server-provider.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.