<commit_before># Agent Check: Traffic Server

## Overview

This check monitors [Traffic Server][1] through the Datadog Agent.

## Setup

Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the [Autodiscovery Integration Templates][3] for guidance on applying these instructions.

### Installation

The Traffic Server check is included in the [Datadog Agent][2] package.

To enable monitoring in Traffic Server, enable the [Stats Over HTTP plugin][10] on your Traffic Server by adding the following line to your `plugin.config` file and reloading Traffic Server:

```
stats_over_http.so
```

### Configuration

1. Edit the `traffic_server.d/conf.yaml` file in the `conf.d/` folder at the root of your Agent's configuration directory to start collecting your Traffic Server performance data. See the [sample traffic_server.d/conf.yaml][4] for all available configuration options.

2. [Restart the Agent][5].

### Validation

[Run the Agent's status subcommand][6] and look for `traffic_server` under the Checks section.<commit_msg>Update readme (#11863)<commit_after># Agent Check: Traffic Server

## Overview

This check monitors [Traffic Server][1] through the Datadog Agent.

## Setup

Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the [Autodiscovery Integration Templates][3] for guidance on applying these instructions.

### Installation

The Traffic Server check is included in the [Datadog Agent][2] package.

To enable monitoring in Traffic Server, enable the [Stats Over HTTP plugin][10] on your Traffic Server by adding the following line to your `plugin.config` file and reloading Traffic Server:

```
stats_over_http.so
```

### Configuration

1. Edit the `traffic_server.d/conf.yaml` file in the `conf.d/` folder at the root of your Agent's configuration directory to start collecting your Traffic Server performance data. See the [sample traffic_server.d/conf.yaml][4] for all available configuration options.

**Note**: When using the default [configuration file][4], not all metrics are collected by default.

Comment out the `metric_patterns` option to collect all available metrics, or edit it to collect a different subset of metrics:

```
    ## @param metric_patterns - mapping - optional
    ## A mapping of metrics to include or exclude, with each entry being a regular expression.
    ##
    ## Metrics defined in `exclude` will take precedence in case of overlap.
    ## Comment out this option to collect all available metrics.
    #
    metric_patterns:
      include:
         - <METRIC_1>
         - <METRIC_2>
```

2. [Restart the Agent][5].

### Validation

[Run the Agent's status subcommand][6] and look for `traffic_server` under the Checks section.
{'fraction_non_alphanumeric': 0.07786741494212557, 'fraction_numerical': 0.009821115398105928, 'mean_word_length': 4.516441005802708, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3678279', 'n_tokens_mistral': 766, 'n_tokens_neox': 726, 'n_words': 362}