Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed formatting error #4207

Merged
merged 1 commit into from
Jan 17, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 16 additions & 11 deletions docs/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -309,6 +309,7 @@ name: <string>
time_intervals:
[ - <time_interval_spec> ... ]
```

#### `<time_interval_spec>`

A `time_interval_spec` contains the actual definition for an interval of time. The syntax
Expand Down Expand Up @@ -339,9 +340,11 @@ make it easy to represent times that start/end on hour boundaries.
For example, `start_time: '17:00'` and `end_time: '24:00'` will begin at 17:00 and finish
immediately before 24:00. They are specified like so:

times:
- start_time: HH:MM
end_time: HH:MM
```yaml
times:
- start_time: HH:MM
end_time: HH:MM
```

`weekday_range`: A list of days of the week, where the week begins on Sunday and ends on Saturday.
Days should be specified by name (e.g. 'Sunday'). For convenience, ranges are also accepted
Expand All @@ -367,10 +370,12 @@ example, `'Australia/Sydney'`. The location provides the time zone for the time
interval. For example, a time interval with a location of `'Australia/Sydney'` that
contained something like:

times:
- start_time: 09:00
end_time: 17:00
weekdays: ['monday:friday']
```yaml
times:
- start_time: 09:00
end_time: 17:00
weekdays: ['monday:friday']
```

would include any time that fell between the hours of 9:00AM and 5:00PM, between Monday
and Friday, using the local time in Sydney, Australia.
Expand Down Expand Up @@ -437,7 +442,6 @@ source_matchers:
# Labels that must have an equal value in the source and target
# alert for the inhibition to take effect.
[ equal: '[' <labelname>, ... ']' ]

```

## Label matchers
Expand Down Expand Up @@ -482,7 +486,7 @@ Any occurrences of disagreement should be looked at on a case by case basis as d

In UTF-8 strict mode, Alertmanager disables support for classic matchers:

```
```bash
alertmanager --config.file=config.yml --enable-feature="utf8-strict-mode"
```

Expand All @@ -498,7 +502,7 @@ UTF-8 strict mode will be the default mode of Alertmanager at the end of the tra

Classic mode is equivalent to Alertmanager versions 0.26.0 and older:

```
```bash
alertmanager --config.file=config.yml --enable-feature="classic-mode"
```

Expand Down Expand Up @@ -1347,13 +1351,15 @@ The fields are documented in the [Rocketchat API documentation](https://develope
```

#### `<rocketchat_action_config>`

The fields are documented in the [Rocketchat API api models](https://github.com/RocketChat/Rocket.Chat.Go.SDK/blob/master/models/message.go).

```yaml
[ type: <tmpl_string> | ignored, only "button" is supported ]
[ text: <tmpl_string> ]
[ url: <tmpl_string> ]
[ msg: <tmpl_string> ]
```

### `<slack_config>`

Expand Down Expand Up @@ -1600,7 +1606,6 @@ url_file: <filepath>
# no timeout should be applied.
# NOTE: This will have no effect if set higher than the group_interval.
[ timeout: <duration> | default = 0s ]

```

The Alertmanager
Expand Down
Loading