Checks, locations & failure confirmation — found from sitemap — Oh Dear

Cited by

Facts read from this source

• Uptime check automatic Report an error

  “Every monitor added to Oh Dear will automatically be checked for uptime. Every time we check the uptime, we also collect and store detailed performance metrics for that website.”

• Monitor types Report an error

  “HTTP monitoring is the most common type and is perfect for monitoring websites and web applications.”

• Ping monitoring Report an error

  “Ping monitoring uses ICMP packets to check if a server is reachable on the network level.”

• Tcp port monitoring Report an error

  “TCP port monitoring checks if specific ports are open and accepting connections.”

• Multi location monitoring Report an error

  “Each monitor is checked from a primary location and verified from a secondary location. You can choose your primary location from within the Oh Dear dashboard.”

• Warning state Report an error

  “Warnings count as online for uptime percentage calculations. They do not create downtime periods and will not reduce your reported uptime.”

• Uptime options Report an error

  “If it responds with a 2xx HTTP response, the check passes.”

• Check string Report an error

  “look for string: we can check if a given string is found on the result. If it is not found, we'll mark the check as failed.”

• Absent string Report an error

  “absent string: we can check if a given string is not present on the result. If it is found, we'll mark the check as failed.”

• Http verbs Report an error

  “http verb: instead of a GET request, you can specify that the check should be performed with a POST, PATCH or PUT HTTP method.”

• Max request headers Report an error

  “request headers: you can specify up to 5 extra HTTP headers that should be used when sending an uptime request to your website.”

• Json payload Report an error

  “On the Payload tab, set "Send it as" to JSON and you'll get a text area to type the body in.”

• Json payload limit Report an error

  “The body can be up to 10,000 characters.”

• Magic variables Report an error

  “you can use magic variables anywhere in your monitor URL, in your custom request headers, or in your POST payload. Right before each check, we replace them with fresh values, so every request is unique enough to bypass the cache.”

• Ping options Report an error

  “Acceptable packet loss: The maximum percentage of packet loss before marking the site as down.”

• Tcp default timeout Report an error

  “Timeout: The maximum time to wait for the TCP connection and response in milliseconds (default: 1000ms).”

• Tcp send string Report an error

  “Send string: An optional string to send after establishing the TCP connection. You can use \r and \n for line breaks (e.g., "EHLO example.com\r\n" for SMTP).”

• Response header verification Report an error

  “We can verify that those headers contain the values you expect. If these expectations are not met, we'll consider your website as down.”

• Body assertions Report an error

  “For endpoints that return JSON, you can go a step further and check the actual values in the response body. If any assertion fails, we'll consider your monitor down, the same way we would for a timeout or a 500.”

• Body assertion conditions Report an error

  “equals matches exactly”

• Body assertion size limit Report an error

  “If the body is empty, isn't valid JSON, or is larger than 2 MB, we can't evaluate it and the check fails with a message that says so.”

• Check frequency Report an error

  “Uptime checks happen every minute from the primary location.”

• Downtime notification threshold Report an error

  “If this is too quick you can increase the number of downtime minutes before a notification in 'Monitors > Settings > Uptime > Notification settings'.”

• Hourly reminders Report an error

  “If your monitor is still down an hour after the first downtime notification, we'll send you another one. We keep sending a reminder every hour until the monitor is back up.”

• Acknowledge alerts Report an error

  “To stop the reminders for an outage you're already working on, acknowledge the alert. You'll still get the recovery notification.”

• Downtime timeout default Report an error

  “That timeout defaults to 5 seconds and can be set anywhere from 1 to 10 seconds per monitor.”

• Detailed reporting Report an error

  “if the website responded with a status code other than HTTP/2xx, we will show you the exact HTTP response headers we received to help you troubleshoot, along with the IP(s) we used to monitor your site.”

• Performance alerts Report an error

  “Hard threshold: if the monitor is continuously slower than this value, we will alert you”

• Performance change detection Report an error

  “We look at the difference between the average response time in the past two hours vs average response time in past 15 minutes.”

• Performance metrics Report an error

  “We will be able to show you the following detailed metrics.”

• Ttfb Report an error

  “The Time To First Byte (or TTFB) is the same as our Remote Server Processing time.”

• Monthly reports Report an error

  “Each month, you'll receive an uptime report for all your monitors to show you how well they performed.”

• Custom headers auth Report an error

  “Yes, you can add custom headers to authenticate Oh Dear to your application through your monitor settings.”

• Monitoring locations Report an error

  “We perform uptime checks from these locations:”

Scores citing this record

• The Agency Developer Checks, locations & failure confirmation
• The Agency Developer Alerting, escalation & on-call
• The Agency Developer Uptime reports, data & the vendor's own reliability
• The Customer Support Lead Checks, locations & failure confirmation
• The Customer Support Lead Alerting, escalation & on-call
• The E-Commerce Operations Manager Checks, locations & failure confirmation
• The E-Commerce Operations Manager Alerting, escalation & on-call
• The E-Commerce Operations Manager Uptime reports, data & the vendor's own reliability
• The SaaS Platform Engineer Checks, locations & failure confirmation
• The SaaS Platform Engineer Alerting, escalation & on-call
• The SaaS Platform Engineer Uptime reports, data & the vendor's own reliability
• The Information Security Officer Checks, locations & failure confirmation
• The Information Security Officer Alerting, escalation & on-call
• The Information Security Officer Uptime reports, data & the vendor's own reliability
• The Skeptic Checks, locations & failure confirmation
• The Skeptic Alerting, escalation & on-call
• The Skeptic Uptime reports, data & the vendor's own reliability