Regenerate integrations docs (#20655)
Co-authored-by: ilyam8 <22274335+ilyam8@users.noreply.github.com>
Netdata bot committed
Jul 11, 2025 at 09:33 UTC
0e59a9068d679389a5a36654c9c4f3c20b911dc6
1 file changed
+5
-5
src/go/plugin/go.d/collector/httpcheck/integrations/http_endpoints.md
+5
-5
@@ -33,7 +33,7 @@ Possible statuses:
33
| redirect | Received a redirect response (3xx status code) while `not_follow_redirects` is configured. |
34
| bad_status | HTTP request completed with a status code outside the configured `status_accepted` range (default: non-200). |
35
| bad_content | HTTP request completed successfully but the response body does not match the expected content (when using `response_match`). |
36
-| bad_header | HTTP request completed successfully but response headers do not match the expected values (when using `headers_match`). |
36
+| bad_header | HTTP request completed successfully but response headers do not match the expected values (when using `header_match`). |
37
38
39
@@ -144,10 +144,10 @@ The following options can be defined globally: update_every, autodetection_retry
144
| url | Server URL. | | yes |
145
| status_accepted | HTTP accepted response statuses. Anything else will result in 'bad status' in the status chart. | [200] | no |
146
| response_match | If the status code is accepted, the content of the response will be matched against this regular expression. | | no |
147
-| headers_match | This option defines a set of rules that check for specific key-value pairs in the HTTP headers of the response. | [] | no |
148
-| headers_match.exclude | This option determines whether the rule should check for the presence of the specified key-value pair or the absence of it. | no | no |
149
-| headers_match.key | The exact name of the HTTP header to check for. | | yes |
150
-| headers_match.value | The [pattern](https://github.com/netdata/netdata/tree/master/src/go/pkg/matcher#supported-format) to match against the value of the specified header. | | no |
147
+| header_match | This option defines a set of rules that check for specific key-value pairs in the HTTP headers of the response. | [] | no |
148
+| header_match.exclude | This option determines whether the rule should check for the presence of the specified key-value pair or the absence of it. | no | no |
149
+| header_match.key | The exact name of the HTTP header to check for. | | yes |
150
+| header_match.value | The [pattern](https://github.com/netdata/netdata/tree/master/src/go/pkg/matcher#supported-format) to match against the value of the specified header. | | no |
151
| cookie_file | Path to cookie file. See [cookie file format](https://everything.curl.dev/http/cookies/fileformat). | | no |
152
| timeout | HTTP request timeout. | 1 | no |
153
| username | Username for basic HTTP authentication. | | no |