HTTP
|
1 Troubleshooting Commands
Contributed by Jonathan Funk
Codecollection:
Check if an HTTP request against a URL fails or times out of a given latency window.
A return of 1 is considered a success, while a 0 is failure.
Tasks:
Tasks:
- Checking HTTP URL Is Available And Timely
Source Code
Troubleshoot and triage a URL to inspect it for common issues such as an expired certification, missing DNS records, etc.
Tasks:
Tasks:
- Validate Platform Egress
- Perform Inspection On URL
A curl SLI for querying and extracting data from a generic curl call. Supports jq. Should prodice a single metric.
Tasks:
Tasks:
- Run Curl Command and Push Metric
A curl TaskSet for querying and extracting data from a generic curl call. Supports jq. Adds results to the report.
Tasks:
Tasks:
- Run Curl Command and Add to Report
Measure HTTP latency against a given URL.
The returned metric is the number of seconds the request took as a float value.
Tasks:
Tasks:
- Check HTTP Latency to Well Known URL
This taskset uses curl to validate the response code of the endpoint. Returns ascore of 1 if healthy, an 0 if unhealthy.
Tasks:
Tasks:
- Validate HTTP URL Availability and Timeliness for ${URL}
This taskset uses curl to validate the response code of the endpoint and provides the total time of the request.
Tasks:
Tasks:
- Check HTTP URL Availability and Timeliness for `URL`
Discoverable
Raises Issues
This taskset queries Jaeger API directly for trace details and parses the results
Tasks:
Tasks:
- Query Traces in Jaeger for Unhealthy HTTP Response Codes in Namespace `NAMESPACE`