Open agardnerIT opened 2 months ago
Pinging code owners:
receiver/httpcheck: @codeboten
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Thanks for opening the issue @agardnerIT! An option to address a similar feature was proposed in https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/27015, adding it here for context.
Going from memory, the discussion in the SIG call was that it would be better to add an attribute to an existing metric rather than adding a separate metric to track this.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Component(s)
receiver/httpcheck
Is your feature request related to a problem? Please describe.
I need to retrieve endpoints and ensure that content is available in the DOM. Just because an endpoint returns a
200 OK
doesn't mean it's healthy. A common pattern these days is to200 OK
return an "Sorry, we ran into an error" page.Describe the solution you'd like
A user should be able to specify a "content match" rule for each endpoint. eg.
"This domain is for use in illustrative examples in documents" in http.response_content
forhttp://example.com
Describe alternatives you've considered
N/A
Additional context
No response