monasca-agent/conf.d/http_check.yaml.example
David Schroeder bac28480bd Remove 'detail' dimension, fix a couple bugs
The 'detail' dimension in http_check is not actually an appropriate
dimension since it does not contain data which _identifies_ a metric.
This data is valuable, though, and will be captured and made available
in a future enhancement.

Bug fixes:
- Fix unix.py crash on EFI mountpoints which return 0 available inodes
- Rename 'service_name' to 'name' in nagios_wrapper for ServicesCheck
  compatibility
- Update nagios_wrapper YAML example for naming convention

Change-Id: I44877a856fac84f54ca764a79e75ace9f90d9302
2014-09-17 15:21:39 -06:00

49 lines
2.0 KiB
Plaintext

init_config:
instances:
# - name: Some Service Name
# url: http://some.url.example.com
# timeout: 1
# If your service uses basic authentication, you can optionally
# specify a username and password that will be used in the check.
# username: user
# password: pass
# The (optional) match_pattern parameter will instruct the check
# to match the HTTP response body against a regular-expression-
# compatible pattern. If the pattern matches the check will
# return 0 for OK. Otherwise, it will return 1 for an error
# match_pattern: '.*OK.*OK.*OK.*OK.*OK'
# The (optional) collect_response_time parameter will instruct the
# check to create a metric 'network.http.response_time', tagged with
# the url, reporting the response time in seconds.
# collect_response_time: true
# The (optional) disable_ssl_validation will instruct the check
# to skip the validation of the SSL certificate of the URL being tested.
# This is mostly useful when checking SSL connections signed with
# certificates that are not themselves signed by a public authority.
# When true, the check logs a warning in collector.log
# disable_ssl_validation: true
# The (optional) headers parameter allows you to send extra headers
# with the request. This is useful for explicitly specifying the host
# header or perhaps adding headers for authorisation purposes. Note
# that the http client library converts all headers to lowercase.
# This is legal according to RFC2616
# (See: http://tools.ietf.org/html/rfc2616#section-4.2)
# but may be problematic with some HTTP servers
# (See: https://code.google.com/p/httplib2/issues/detail?id=169)
# headers:
# Host: alternative.host.example.com
# X-Auth-Token: SOME-AUTH-TOKEN
# dimensions:
# dim1: value1