⛑ Gatus - Automated service health dashboard

Overview

Gatus

build Go Report Card codecov Go version Docker pulls Follow TwinProduction

A service health dashboard in Go that is meant to be used as a docker image with a custom configuration file.

I personally deploy it in my Kubernetes cluster and let it monitor the status of my core applications: https://status.twinnation.org/

Table of Contents

Features

The main features of Gatus are:

  • Highly flexible health check conditions: While checking the response status may be enough for some use cases, Gatus goes much further and allows you to add conditions on the response time, the response body and even the IP address.
  • Ability to use Gatus for user acceptance tests: Thanks to the point above, you can leverage this application to create automated user acceptance tests.
  • Very easy to configure: Not only is the configuration designed to be as readable as possible, it's also extremely easy to add a new service or a new endpoint to monitor.
  • Alerting: While having a pretty visual dashboard is useful to keep track of the state of your application(s), you probably don't want to stare at it all day. Thus, notifications via Slack, Mattermost, Messagebird, PagerDuty and Twilio are supported out of the box with the ability to configure a custom alerting provider for any needs you might have, whether it be a different provider or a custom application that manages automated rollbacks.
  • Metrics
  • Low resource consumption: As with most Go applications, the resource footprint that this application requires is negligibly small.
  • GitHub uptime badges: Uptime 1h Uptime 24h Uptime 7d
  • Service auto discovery in Kubernetes (ALPHA)

Usage

By default, the configuration file is expected to be at config/config.yaml.

You can specify a custom path by setting the GATUS_CONFIG_FILE environment variable.

Here's a simple example:

metrics: true         # Whether to expose metrics at /metrics
services:
  - name: twinnation  # Name of your service, can be anything
    url: "https://twinnation.org/health"
    interval: 30s     # Duration to wait between every status check (default: 60s)
    conditions:
      - "[STATUS] == 200"         # Status must be 200
      - "[BODY].status == UP"     # The json path "$.status" must be equal to UP
      - "[RESPONSE_TIME] < 300"   # Response time must be under 300ms
  - name: example
    url: "https://example.org/"
    interval: 30s
    conditions:
      - "[STATUS] == 200"

This example would look like this:

Simple example

Note that you can also add environment variables in the configuration file (i.e. $DOMAIN, ${DOMAIN})

Configuration

Parameter Description Default
debug Whether to enable debug logs false
metrics Whether to expose metrics at /metrics false
storage Storage configuration {}
storage.file File to persist the data in. If not set, storage is in-memory only. ""
services List of services to monitor Required []
services[].name Name of the service. Can be anything. Required ""
services[].group Group name. Used to group multiple services together on the dashboard. See Service groups. ""
services[].url URL to send the request to Required ""
services[].method Request method GET
services[].insecure Whether to skip verifying the server's certificate chain and host name false
services[].conditions Conditions used to determine the health of the service []
services[].interval Duration to wait between every status check 60s
services[].graphql Whether to wrap the body in a query param ({"query":"$body"}) false
services[].body Request body ""
services[].headers Request headers {}
services[].dns Configuration for a service of type DNS. See Monitoring using DNS queries ""
services[].dns.query-type Query type for DNS service ""
services[].dns.query-name Query name for DNS service ""
services[].alerts[].type Type of alert. Valid types: slack, pagerduty, twilio, mattermost, messagebird, custom Required ""
services[].alerts[].enabled Whether to enable the alert false
services[].alerts[].failure-threshold Number of failures in a row needed before triggering the alert 3
services[].alerts[].success-threshold Number of successes in a row before an ongoing incident is marked as resolved 2
services[].alerts[].send-on-resolved Whether to send a notification once a triggered alert is marked as resolved false
services[].alerts[].description Description of the alert. Will be included in the alert sent ""
alerting Configuration for alerting {}
alerting.slack Configuration for alerts of type slack {}
alerting.slack.webhook-url Slack Webhook URL Required ""
alerting.pagerduty Configuration for alerts of type pagerduty {}
alerting.pagerduty.integration-key PagerDuty Events API v2 integration key. Required ""
alerting.twilio Settings for alerts of type twilio {}
alerting.twilio.sid Twilio account SID Required ""
alerting.twilio.token Twilio auth token Required ""
alerting.twilio.from Number to send Twilio alerts from Required ""
alerting.twilio.to Number to send twilio alerts to Required ""
alerting.mattermost Configuration for alerts of type mattermost {}
alerting.mattermost.webhook-url Mattermost Webhook URL Required ""
alerting.mattermost.insecure Whether to skip verifying the server's certificate chain and host name false
alerting.messagebird Settings for alerts of type messagebird {}
alerting.messagebird.access-key Messagebird access key Required ""
alerting.messagebird.originator The sender of the message Required ""
alerting.messagebird.recipients The recipients of the message Required ""
alerting.custom Configuration for custom actions on failure or alerts {}
alerting.custom.url Custom alerting request url Required ""
alerting.custom.method Request method GET
alerting.custom.insecure Whether to skip verifying the server's certificate chain and host name false
alerting.custom.body Custom alerting request body. ""
alerting.custom.headers Custom alerting request headers {}
security Security configuration {}
security.basic Basic authentication security configuration {}
security.basic.username Username for Basic authentication Required ""
security.basic.password-sha512 Password's SHA512 hash for Basic authentication Required ""
disable-monitoring-lock Whether to disable the monitoring lock false
web Web configuration {}
web.address Address to listen on 0.0.0.0
web.port Port to listen on 8080

For Kubernetes configuration, see Kubernetes

Conditions

Here are some examples of conditions you can use:

Condition Description Passing values Failing values
[STATUS] == 200 Status must be equal to 200 200 201, 404, ...
[STATUS] < 300 Status must lower than 300 200, 201, 299 301, 302, ...
[STATUS] <= 299 Status must be less than or equal to 299 200, 201, 299 301, 302, ...
[STATUS] > 400 Status must be greater than 400 401, 402, 403, 404 400, 200, ...
[STATUS] == any(200, 429) Status must be either 200 or 420 200, 429 201, 400, ...
[CONNECTED] == true Connection to host must've been successful true, false
[RESPONSE_TIME] < 500 Response time must be below 500ms 100ms, 200ms, 300ms 500ms, 501ms
[IP] == 127.0.0.1 Target IP must be 127.0.0.1 127.0.0.1 0.0.0.0
[BODY] == 1 The body must be equal to 1 1 {}, 2, ...
[BODY].user.name == john JSONPath value of $.user.name is equal to john {"user":{"name":"john"}}
[BODY].data[0].id == 1 JSONPath value of $.data[0].id is equal to 1 {"data":[{"id":1}]}
[BODY].age == [BODY].id JSONPath value of $.age is equal JSONPath $.id {"age":1,"id":1}
len([BODY].data) < 5 Array at JSONPath $.data has less than 5 elements {"data":[{"id":1}]}
len([BODY].name) == 8 String at JSONPath $.name has a length of 8 {"name":"john.doe"} {"name":"bob"}
[BODY].name == pat(john*) String at JSONPath $.name matches pattern john* {"name":"john.doe"} {"name":"bob"}
[BODY].id == any(1, 2) Value at JSONPath $.id is equal to 1 or 2 1, 2 3, 4, 5
[CERTIFICATE_EXPIRATION] > 48h Certificate expiration is more than 48h away 49h, 50h, 123h 1h, 24h, ...

Placeholders

Placeholder Description Example of resolved value
[STATUS] Resolves into the HTTP status of the request 404
[RESPONSE_TIME] Resolves into the response time the request took, in ms 10
[IP] Resolves into the IP of the target host 192.168.0.232
[BODY] Resolves into the response body. Supports JSONPath. {"name":"john.doe"}
[CONNECTED] Resolves into whether a connection could be established true
[CERTIFICATE_EXPIRATION] Resolves into the duration before certificate expiration 24h, 48h, 0 (if not using HTTPS)
[DNS_RCODE] Resolves into the DNS status of the response NOERROR

Functions

Function Description Example
len Returns the length of the object/slice. Works only with the [BODY] placeholder. len([BODY].username) > 8
pat Specifies that the string passed as parameter should be evaluated as a pattern. Works only with == and !=. [IP] == pat(192.168.*)
any Specifies that any one of the values passed as parameters is a valid value. Works only with == and !=. [BODY].ip == any(127.0.0.1, ::1)

NOTE: Use pat only when you need to. [STATUS] == pat(2*) is a lot more expensive than [STATUS] < 300.

Alerting

Configuring Slack alerts

alerting:
  slack: 
    webhook-url: "https://hooks.slack.com/services/**********/**********/**********"
services:
  - name: twinnation
    url: "https://twinnation.org/health"
    interval: 30s
    alerts:
      - type: slack
        enabled: true
        description: "healthcheck failed 3 times in a row"
        send-on-resolved: true
      - type: slack
        enabled: true
        failure-threshold: 5
        description: "healthcheck failed 5 times in a row"
        send-on-resolved: true
    conditions:
      - "[STATUS] == 200"
      - "[BODY].status == UP"
      - "[RESPONSE_TIME] < 300"

Here's an example of what the notifications look like:

Slack notifications

Configuring PagerDuty alerts

It is highly recommended to set services[].alerts[].send-on-resolved to true for alerts of type pagerduty, because unlike other alerts, the operation resulting from setting said parameter to true will not create another incident, but mark the incident as resolved on PagerDuty instead.

alerting:
  pagerduty: 
    integration-key: "********************************"
services:
  - name: twinnation
    url: "https://twinnation.org/health"
    interval: 30s
    alerts:
      - type: pagerduty
        enabled: true
        failure-threshold: 3
        success-threshold: 5
        send-on-resolved: true
        description: "healthcheck failed 3 times in a row"
    conditions:
      - "[STATUS] == 200"
      - "[BODY].status == UP"
      - "[RESPONSE_TIME] < 300"

Configuring Twilio alerts

alerting:
  twilio:
    sid: "..."
    token: "..."
    from: "+1-234-567-8901"
    to: "+1-234-567-8901"
services:
  - name: twinnation
    interval: 30s
    url: "https://twinnation.org/health"
    alerts:
      - type: twilio
        enabled: true
        failure-threshold: 5
        send-on-resolved: true
        description: "healthcheck failed 5 times in a row"
    conditions:
      - "[STATUS] == 200"
      - "[BODY].status == UP"
      - "[RESPONSE_TIME] < 300"

Configuring Mattermost alerts

alerting:
  mattermost: 
    webhook-url: "http://**********/hooks/**********"
    insecure: true
services:
  - name: twinnation
    url: "https://twinnation.org/health"
    interval: 30s
    alerts:
      - type: mattermost
        enabled: true
        description: "healthcheck failed 3 times in a row"
        send-on-resolved: true
    conditions:
      - "[STATUS] == 200"
      - "[BODY].status == UP"
      - "[RESPONSE_TIME] < 300"

Here's an example of what the notifications look like:

Mattermost notifications

Configuring Messagebird alerts

Example of sending SMS text message alert using Messagebird:

alerting:
  messagebird:
    access-key: "..."
    originator: "31619191918"
    recipients: "31619191919,31619191920"
services:
  - name: twinnation
    interval: 30s
    url: "https://twinnation.org/health"
    alerts:
      - type: messagebird
        enabled: true
        failure-threshold: 3
        send-on-resolved: true
        description: "healthcheck failed 3 times in a row"
    conditions:
      - "[STATUS] == 200"
      - "[BODY].status == UP"
      - "[RESPONSE_TIME] < 300"

Configuring custom alerts

While they're called alerts, you can use this feature to call anything.

For instance, you could automate rollbacks by having an application that keeps tracks of new deployments, and by leveraging Gatus, you could have Gatus call that application endpoint when a service starts failing. Your application would then check if the service that started failing was recently deployed, and if it was, then automatically roll it back.

The values [ALERT_DESCRIPTION] and [SERVICE_NAME] are automatically substituted for the alert description and the service name respectively in the body (alerting.custom.body) as well as the url (alerting.custom.url).

If you have send-on-resolved set to true, you may want to use [ALERT_TRIGGERED_OR_RESOLVED] to differentiate the notifications. It will be replaced for either TRIGGERED or RESOLVED, based on the situation.

For all intents and purpose, we'll configure the custom alert with a Slack webhook, but you can call anything you want.

alerting:
  custom:
    url: "https://hooks.slack.com/services/**********/**********/**********"
    method: "POST"
    insecure: true
    body: |
      {
        "text": "[ALERT_TRIGGERED_OR_RESOLVED]: [SERVICE_NAME] - [ALERT_DESCRIPTION]"
      }
services:
  - name: twinnation
    url: "https://twinnation.org/health"
    interval: 30s
    alerts:
      - type: custom
        enabled: true
        failure-threshold: 10
        success-threshold: 3
        send-on-resolved: true
        description: "healthcheck failed 10 times in a row"
    conditions:
      - "[STATUS] == 200"
      - "[BODY].status == UP"
      - "[RESPONSE_TIME] < 300"

Kubernetes (ALPHA)

WARNING: This feature is in ALPHA. This means that it is very likely to change in the near future, which means that while you can use this feature as you see fit, there may be breaking changes in future releases.

Parameter Description Default
kubernetes Kubernetes configuration {}
kubernetes.auto-discover Whether to enable auto discovery false
kubernetes.cluster-mode Cluster mode to use for authenticating. Supported values: in, out Required ""
kubernetes.service-template Service template. See services[] in Configuration Required nil
kubernetes.excluded-service-suffixes List of service suffixes to not monitor (e.g. canary) []
kubernetes.namespaces List of configurations for the namespaces from which services will be discovered []
kubernetes.namespaces[].name Namespace name Required ""
kubernetes.namespaces[].hostname-suffix Suffix to append to the service name before calling target-path Required ""
kubernetes.namespaces[].target-path Path that will be called on the discovered service for the health check ""
kubernetes.namespaces[].excluded-services List of services to not monitor in the given namespace []

Auto Discovery

Auto discovery works by reading all Service resources from the configured namespaces and appending the hostname-suffix as well as the configured target-path to the service name and making an HTTP call.

All auto-discovered services will have the service configuration populated from the service-template.

You can exclude certain services from the dashboard by using kubernetes.excluded-service-suffixes or kubernetes.namespaces[].excluded-services.

kubernetes:
  auto-discover: true
  # out: Gatus is deployed outside of the K8s cluster.
  # in: Gatus is deployed in the K8s cluster
  cluster-mode: "out"                                              
  excluded-service-suffixes:
    - canary
  service-template:
    interval: 30s
    conditions:
      - "[STATUS] == 200"
  namespaces:
    - name: default
      # If cluster-mode is out, you should use an externally accessible hostname suffix (e.g.. .example.com)
      # This will result in gatus generating services with URLs like <service-name>.example.com
      # If cluster-mode is in, you can use either an externally accessible hostname suffix (e.g.. .example.com)
      # or an internally accessible hostname suffix (e.g. .default.svc.cluster.local)
      hostname-suffix: ".default.svc.cluster.local"
      target-path: "/health"
      # If some services cannot be or do not need to be monitored, you can exclude them by explicitly defining them
      # in the following list.
      excluded-services:
        - gatus
        - kubernetes

Note that hostname-suffix could also be something like .yourdomain.com, in which case the endpoint that would be monitored would be potato.example.com/health, assuming you have a service named potato and a matching ingress to map potato.example.com to the potato service.

Deploying

See example/kubernetes-with-auto-discovery

Docker

Other than using one of the examples provided in the examples folder, you can also try it out locally by creating a configuration file - we'll call it config.yaml for this example - and running the following command:

docker run -p 8080:8080 --mount type=bind,source="$(pwd)"/config.yaml,target=/config/config.yaml --name gatus twinproduction/gatus

If you're on Windows, replace "$(pwd)" by the absolute path to your current directory, e.g.:

docker run -p 8080:8080 --mount type=bind,source=C:/Users/Chris/Desktop/config.yaml,target=/config/config.yaml --name gatus twinproduction/gatus

Running the tests

go test ./... -mod vendor

Using in Production

See the example folder.

FAQ

Sending a GraphQL request

By setting services[].graphql to true, the body will automatically be wrapped by the standard GraphQL query parameter.

For instance, the following configuration:

services:
  - name: filter users by gender
    url: http://localhost:8080/playground
    method: POST
    graphql: true
    body: |
      {
        user(gender: "female") {
          id
          name
          gender
          avatar
        }
      }
    headers:
      Content-Type: application/json # XXX: as of v1.9.2, this header is automatically added when graphql is set to true
    conditions:
      - "[STATUS] == 200"
      - "[BODY].data.user[0].gender == female"

will send a POST request to http://localhost:8080/playground with the following body:

{"query":"      {\n        user(gender: \"female\") {\n          id\n          name\n          gender\n          avatar\n        }\n      }"}

Recommended interval

NOTE: This does not really apply if disable-monitoring-lock is set to true, as the monitoring lock is what tells Gatus to only evaluate one service at a time.

To ensure that Gatus provides reliable and accurate results (i.e. response time), Gatus only evaluates one service at a time In other words, even if you have multiple services with the exact same interval, they will not execute at the same time.

You can test this yourself by running Gatus with several services configured with a very short, unrealistic interval, such as 1ms. You'll notice that the response time does not fluctuate - that is because while services are evaluated on different goroutines, there's a global lock that prevents multiple services from running at the same time.

Unfortunately, there is a drawback. If you have a lot of services, including some that are very slow or prone to time out (the default time out is 10s for HTTP and 5s for TCP), then it means that for the entire duration of the request, no other services can be evaluated.

This does mean that Gatus will be unable to evaluate the health of other services. The interval does not include the duration of the request itself, which means that if a service has an interval of 30s and the request takes 2s to complete, the timestamp between two evaluations will be 32s, not 30s.

While this does not prevent Gatus' from performing health checks on all other services, it may cause Gatus to be unable to respect the configured interval, for instance:

  • Service A has an interval of 5s, and times out after 10s to complete
  • Service B has an interval of 5s, and takes 1ms to complete
  • Service B will be unable to run every 5s, because service A's health evaluation takes longer than its interval

To sum it up, while Gatus can really handle any interval you throw at it, you're better off having slow requests with higher interval.

As a rule of the thumb, I personally set interval for more complex health checks to 5m (5 minutes) and simple health checks used for alerting (PagerDuty/Twilio) to 30s.

Default timeouts

Protocol Timeout
HTTP 10s
TCP 5s

Monitoring a TCP service

By prefixing services[].url with tcp:\\, you can monitor TCP services at a very basic level:

services:
  - name: redis
    url: "tcp://127.0.0.1:6379"
    interval: 30s
    conditions:
      - "[CONNECTED] == true"

Placeholders [STATUS] and [BODY] as well as the fields services[].body, services[].insecure, services[].headers, services[].method and services[].graphql are not supported for TCP services.

NOTE: [CONNECTED] == true does not guarantee that the service itself is healthy - it only guarantees that there's something at the given address listening to the given port, and that a connection to that address was successfully established.

Monitoring a service using ICMP

By prefixing services[].url with icmp:\\, you can monitor services at a very basic level using ICMP, or more commonly known as "ping" or "echo":

services:
  - name: ICMP
    url: "icmp://example.com"
    conditions:
      - "[CONNECTED] == true"

Only the placeholders [CONNECTED], [IP] and [RESPONSE_TIME] are supported for services of type ICMP. You can specify a domain prefixed by icmp://, or an IP address prefixed by icmp://.

Monitoring a service using DNS queries

Defining a dns configuration in a service will automatically mark that service as a service of type DNS:

services:
  - name: example dns query
    url: "8.8.8.8" # Address of the DNS server to use
    interval: 30s
    dns:
      query-name: "example.com"
      query-type: "A"
    conditions:
      - "[BODY] == 93.184.216.34"
      - "[DNS_RCODE] == NOERROR"

There are two placeholders that can be used in the conditions for services of type DNS:

  • The placeholder [BODY] resolves to the output of the query. For instance, a query of type A would return an IPv4.
  • The placeholder [DNS_RCODE] resolves to the name associated to the response code returned by the query, such as NOERROR, FORMERR, SERVFAIL, NXDOMAIN, etc.

Basic authentication

You can require Basic authentication by leveraging the security.basic configuration:

security:
  basic:
    username: "john.doe"
    password-sha512: "6b97ed68d14eb3f1aa959ce5d49c7dc612e1eb1dafd73b1e705847483fd6a6c809f2ceb4e8df6ff9984c6298ff0285cace6614bf8daa9f0070101b6c89899e22"

The example above will require that you authenticate with the username john.doe as well as the password hunter2.

disable-monitoring-lock

Setting disable-monitoring-lock to true means that multiple services could be monitored at the same time.

While this behavior wouldn't generally be harmful, conditions using the [RESPONSE_TIME] placeholder could be impacted by the evaluation of multiple services at the same time, therefore, the default value for this parameter is false.

There are three main reasons why you might want to disable the monitoring lock:

  • You're using Gatus for load testing (each services are periodically evaluated on a different goroutine, so technically, if you create 100 services with a 1 seconds interval, Gatus will send 100 requests per second)
  • You have a lot of services to monitor
  • You want to test multiple services at very short interval (< 5s)

Service groups

Service groups are used for grouping multiple services together on the dashboard.

services:
  - name: frontend
    group: core
    url: "https://example.org/"
    interval: 5m
    conditions:
      - "[STATUS] == 200"

  - name: backend
    group: core
    url: "https://example.org/"
    interval: 5m
    conditions:
      - "[STATUS] == 200"

  - name: monitoring
    group: internal
    url: "https://example.org/"
    interval: 5m
    conditions:
      - "[STATUS] == 200"

  - name: nas
    group: internal
    url: "https://example.org/"
    interval: 5m
    conditions:
      - "[STATUS] == 200"

  - name: random service that isn't part of a group
    url: "https://example.org/"
    interval: 5m
    conditions:
      - "[STATUS] == 200"

The configuration above will result in a dashboard that looks like this:

Gatus Service Groups

Exposing Gatus on a custom port

By default, Gatus is exposed on port 8080, but you may specify a different port by setting the web.port parameter:

web:
  port: 8081

If you're using a PaaS like Heroku that doesn't let you set a custom port and exposes it through an environment variable instead, you can use that environment variable directly in the configuration file:

web:
  port: ${PORT}

Uptime badges

Uptime 1h Uptime 24h Uptime 7d

Gatus can automatically generate a SVG badge for one of your monitored services. This allows you to put badges in your individual services' README or even create your own status page, if you desire.

The endpoint to generate a badge is the following:

/api/v1/badges/uptime/{duration}/{identifier}.svg

Where:

  • {duration} is 7d, 24h or 1h
  • {identifier} has the pattern <GROUP_NAME>_<SERVICE_NAME>.svg in which both variables have , /, _, , and . replaced by -.

For instance, if you want the uptime during the last 24 hours from the service frontend in the group core, the URL would look like this:

http://example.com/api/v1/badges/uptime/7d/core_frontend.svg

If you want to display a service that is not part of a group, you must leave the group value empty:

http://example.com/api/v1/badges/uptime/7d/_frontend.svg

Example: Uptime 24h

![Uptime 24h](https://status.twinnation.org/api/v1/badges/uptime/24h/core_twinnation-external.svg)

If you'd like to see a visual example of each badges available, you can simply navigate to the service's detail page.

Comments
  • Add html content check condition

    Add html content check condition

    As mentioned in my previous issue #61 i'm currently using healthchecks, and the last feature i would need is some generic content regex / string presence check. now, i might be missing something everybody already knows, since you have this BODY placeholder, and maybe that's just it.

    anyway, it seems that the process basically would mean gatus curls the site content and runs a regex or literal string against it, and when it finds it, test passes.

    what do you think?

    in terms of performance, i think that this is actually the most heavy that healthchecks is doing, but already now i'm running all the tests in parallel, and gatus outperforms healthchecks by magnitudes. so nice.

    opened by whysthatso 17
  • Redirection checks are not working

    Redirection checks are not working

    First of all, thanks for such a simple tool and for making it open source :) I tried to see if the following issue was posted already, but I couldn't find anything.

    All my 301 and 302 checks are failing, and it seems to be because when making the HTTP requests, it's following redirects by default.

    Here's an example. https://inbox.google.com does a 301 to https://mail.google.com/, but the status code in the image below is 200.

    Is this by design?

    image

    opened by omederos 14
  • Scalability limits?

    Scalability limits?

    I'm monitoring around 50-55 services with gatus, most are HTTP and 29 of them are using the pat keyword (with wildcards, so about as expensive a query as it can get). All using the default poll interval of 60s.

    I am starting to see some responses of context deadline exceeded (Client.Timeout exceeded while awaiting headers) in the body check. I have manually checked the services in question and they're healthy. Restarting gatus, or just waiting a few minutes seems to resolve this. This does not occur continuously, but have seen it twice in the space of a few hours.

    I can only assume that this is due to a concurrency issue, as it's more than possible that the combination of service times takes longer than 60s to respond. I do not know enough of the gatus architecture to know if this is a problem or not.

    I am running v2.3.0 with #100 changed locally (as I've not updated since I tested it). I will repeat the test with 2.4.0 and report the results here.

    opened by dchidell 13
  • Support grouping services

    Support grouping services

    Supporting service groups could allow a cuter front end experience.

    i.e.

    services:
      - name: k8s-cluster-watch-dog
        url: http://k8s-cluster-watch-dog-v1.tools-${ENVIRONMENT}:8080/health
        group: core         <-------
        interval: 1m
        conditions:
          - "[STATUS] == 200"
          - "[BODY].status == UP"
      - name: prometheus
        url: http://prometheus-operator-prometheus.kube-system:9090/-/healthy
        group: core         <-------
        interval: 1m
        conditions:
          - "[STATUS] == 200"
          - "[BODY] == Prometheus is Healthy."
    

    would generate a dashboard that puts both k8s-cluster-watch-dog and prometheus under the "core" folder.

    image

    Could also support tags, and allow filtering by tags instead

    i.e.

    services:
      - name: k8s-cluster-watch-dog
        url: http://k8s-cluster-watch-dog-v1.tools-${ENVIRONMENT}:8080/health
        tags:              <-------
          - core
        interval: 1m
        conditions:
          - "[STATUS] == 200"
          - "[BODY].status == UP"
      - name: prometheus
        url: http://prometheus-operator-prometheus.kube-system:9090/-/healthy
        tags:              <-------
          - core
          - metrics
        interval: 1m
        conditions:
          - "[STATUS] == 200"
          - "[BODY] == Prometheus is Healthy."
    

    image

    Forgive the terrible drafts, just thought of this on the fly.

    feature 
    opened by TwiN 13
  • ICMP does not work on Mac OS

    ICMP does not work on Mac OS

    MAC OS Big Sur version 11.0.1

    Everything works perfectly ok except icmp in MAC OS.

    Config:

    • name: node-1 url: "icmp://104.237.x.x" group: Uptime (Ping) conditions:
      • "[CONNECTED] == true"
      • "[RESPONSE_TIME] > 0"

    image

    the x.x is in ip is set intentionally.

    Is this wrong config?

    bug good first issue 
    opened by xoraingroup 12
  • Support wecom alerting provider

    Support wecom alerting provider

    Hello, I'm a Chinese and my team use Wechat Company (Wecom) to watch status of servers.

    I'm not a developer, I try to write wecom alerting code and it work's fine on my machine. But because of my Go language level, there may be many exceptions that have not been handled. If possible, I hope it can be merge into the official code. Thanks.

    Push to Wecom, we need 3 necessary parameters, Aid, Cid and Secret.

    package wecom
    
    import (
    	"encoding/json"
    	"fmt"
    	"io/ioutil"
    	"net/http"
    
    	"github.com/TwinProduction/gatus/alerting/alert"
    	"github.com/TwinProduction/gatus/alerting/provider/custom"
    	"github.com/TwinProduction/gatus/core"
    )
    
    // AlertProvider is the configuration necessary for sending an alert using Wecom
    type AlertProvider struct {
    	Aid    string `yaml:"aid"`
    	Cid    string `yaml:"cid"`
    	Secret string `yaml:"secret"`
    	ToUser string `yaml:"touser"` // Not necessary
    	ToParty string `yaml:"toparty"` // Not necessary
    
    	// DefaultAlert is the default alert configuration to use for services with an alert of the appropriate type
    	DefaultAlert *alert.Alert `yaml:"default-alert"`
    }
    

    Then, we need use Cid and Secret to get accessToken.

    	var wetoken string
    	wetoken = fmt.Sprintf("%s%s%s%s", "https://qyapi.weixin.qq.com/cgi-bin/gettoken?corpid=", provider.Cid, "&corpsecret=", provider.Secret)
    	client := &http.Client{}
    	req, err := http.NewRequest("GET", wetoken, nil)
    	resp, err := client.Do(req)
    	if err != nil {
    		fmt.Println("Failure : ", err)
    	}
    	respBody, _ := ioutil.ReadAll(resp.Body)
    	r := make(map[string]interface{})
    	json.Unmarshal([]byte(respBody), &r)
    	accessToken := r["access_token"]
    

    Last, use accessToken to push.

    	return &custom.AlertProvider{
    		URL:    fmt.Sprintf("https://qyapi.weixin.qq.com/cgi-bin/message/send?access_token=%s", accessToken),
    		Method: http.MethodPost,
    		Body: fmt.Sprintf( TODO:BODY ),
    		Headers: map[string]string{"Content-Type": "application/json"},
    	}
    

    If ToUser and ToParty are empty, the BODY will be:

    {
    	"agentid": %s,
    	"msgtype": "text",
    	"text": {
    		"content": "%s"
    	},
    	"duplicate_check_interval": 180
    }
    

    If one of the two is empty, the BODY will be:

    {
    	"toparty": %s,
    	"agentid": %s,
    	"msgtype": "text",
    	"text": {
    		"content": "%s"
    	},
    	"duplicate_check_interval": 180
    }
    

    or

    {
    	"touser": %s,
    	"agentid": %s,
    	"msgtype": "text",
    	"text": {
    		"content": "%s"
    	},
    	"duplicate_check_interval": 180
    }
    

    If both parameters are not empty, the BODY will be:

    {
    	"touser": %s,
    	"toparty": %s,
    	"agentid": %s,
    	"msgtype": "text",
    	"text": {
    		"content": "%s"
    	},
    	"duplicate_check_interval": 180
    }
    
    feature alerting 
    opened by Chandler-Lu 11
  • Implement Postgres as a storage solution

    Implement Postgres as a storage solution

    I stumbled on this neat status page solution the other day and am trying it out, cool stuff!

    I see Store is an interface, and that there is one implementation (in-memory cache with a file used to persist over restarts). However I think it's missing some way to persist the observed results which is more usable in a stateless container, where you don't want to write to a file system.

    Is there perhaps already some extension out there that provides a Store backed by e.g. Redis or Postgres? I would not mind contributing, but if the effort had already been made then that would be unnecessary.

    The point would not be to enable some high availability configuration (I think that would add quite a bit more synchronization work), but simply being able to restart or reconfigure gatus without losing the previous results would be nice.

    Also, the auto save interval could be made configurable.

    feature 
    opened by fabjan 11
  • feat(metrics): Add more metrics (e.g. duration)

    feat(metrics): Add more metrics (e.g. duration)

    Describe the feature request

    In this project https://github.com/prometheus/blackbox_exporter, many metrics like probe_success, probe_duration etc... provided. And in dns probe https://github.com/prometheus/blackbox_exporter/blob/master/prober/dns.go#L129 also has metrics for dns.

    Why do you personally want this feature to be implemented?

    Maybe we can add these metrics in gatus, and user can scrpe to promethus and make dashboard on Grafana.

    How long have you been using this project?

    3 month

    Additional information

    If the team agrees to add this feature, I can submit PR to contribute gatus

    feature 
    opened by wei840222 10
  • Change license to Apache 2

    Change license to Apache 2

    Call me indecisive if you want, since I've done this once before (see 70c9c4b87c8e595f4374b895853312cefc2152f2), but after thing about the pros and cons, I decided that Apache 2 offers better protection for Gatus.

    Long story short:

    • v0.0.1 to v1.3.0: Apache 2
    • v1.3.1 to v3.3.5: MIT
    • v3.3.6 and up: Apache 2

    This PR is here for traceability.

    opened by TwiN 10
  • Bind mounted config.yaml does not automatically reload

    Bind mounted config.yaml does not automatically reload

    Step to reproduce:

    $ cat config/config.yaml
    services:
      - name: example
        url: "https://example.org/"
        interval: 30s
        conditions:
          - "[STATUS] == 200"
    
    $ docker run \
        --rm \
        -p 8080:8080 \
        -v "$(pwd)"/config/config.yaml:/config/config.yaml \
        twinproduction/gatus
    

    Change the name field in the config/config.yaml.

    Observation:

    In the HasLoadedConfigurationFileBeenModified function, the result of the comparison of config.lastFileModTime.Unix() != fileInfo.ModTime().Unix() is always false.

    bug 
    opened by roycyt 10
  • feat(client): Added client configuration option for using a custom DNS resolver

    feat(client): Added client configuration option for using a custom DNS resolver

    Added a new configuration option to the client to allow the user to specify a custom DNS resolver.

    Example config:

    # use Cloudflare DNS to lookup the DNS name for the endpoint
    endpoints:
      - name: front-end
        group: core
        url: "https://twin.sh/health"
        interval: 30s
        client:
          dns-resolver: "tcp://1.1.1.1:53"
        conditions:
          - "[STATUS] == 200"
          - "[BODY].status == UP"
          - "[RESPONSE_TIME] < 150"
    

    Checklist

    • [X] Tested and/or added tests to validate that the changes work as intended, if applicable.
    • [X] Added the documentation in README.md, if applicable.
    opened by tiwood 9
  • oauth2 token add to header as Bearer Token

    oauth2 token add to header as Bearer Token

    Describe the bug

    need a way to add Authorization header with the Bearer token that is got by the oauth2 configuration.

    What do you see?

    I keep seeing endpoint success=false. I have added the oauth2 configuration which is correct, but the token needs to be added as a Header of Authorization = Bearer

    What do you expect to see?

    even with the oauth2 configuration I'm still seeing endpoint success=false

    List the steps that must be taken to reproduce this issue

    deploy helm chart configure oauth2 add POST for an API

    Version

    v4.2.0

    Additional information

    none

    bug 
    opened by dnltech2020 0
  • Support UDP endpoints

    Support UDP endpoints

    Describe the feature request

    DNS servers and some VPN servers like OpenVPN work on UDP protocol. Check availability for these services possibly only by checking UDP port

    Why do you personally want this feature to be implemented?

    I want check availability of some my VPN servers

    How long have you been using this project?

    1 year

    Additional information

    Based on TCP check it can look like this:

    endpoints:
      - name: dns
        url: "udp://127.0.0.1:53"
        interval: 30s
        conditions:
          - "[CONNECTED] == true"
    
    feature 
    opened by belaytzev 0
  • fix(ui): center and fixed navigation arrows

    fix(ui): center and fixed navigation arrows

    Summary

    • Centered Navigation arrows
    • keep them fixed

    When the number of endpoints is large, we had to scroll down to navigate through timeline. This patch makes navigation quicker.

    Checklist

    • [ ] Added the documentation in README.md, if applicable.
    • [ ] Tested and/or added tests to validate that the changes work as intended, if applicable.
    opened by shashank68 0
  • Endpoint detail page for remote instances

    Endpoint detail page for remote instances

    Summary

    Fixes: #329

    Checklist

    • [X] Tested and/or added tests to validate that the changes work as intended, if applicable.
    • [x] Added the documentation in README.md, if applicable.
    opened by praveen-livspace 0
  • Detail page of remote endpoints throw 404

    Detail page of remote endpoints throw 404

    Describe the bug

    Clicking on any of the remote endpoint on the main page takes to a 404 page.

    What do you see?

    A blank detail page

    What do you expect to see?

    Detailed status of the remote endpoint.

    List the steps that must be taken to reproduce this issue

    1. Start the application with a remote endpoint.
    2. Click on the remote endpoint hyperlink.
    3. Notice that the detail page does not show any data.

    Version

    4.1.0

    Additional information

    No response

    bug 
    opened by praveen-livspace 2
  • Add

    Add "username" and "password" as optional Oauth 2.0 authentication

    Describe the feature request

    Hi! It would be really useful to be able to add in the client side yaml config file an option to add username and password. This because some web services rely on that data to create a special token. It could be something like: endpoints: - name: "/webservice/endpoint" url: "https://some-url/" client: oauth2: token-url: https://auth.com/protocol/openid-connect/token client-id: something-client client-secret: something-password scopes: ["scope"] interval: 5m group: Web Service conditions: - "[STATUS] == 200"

    Why do you personally want this feature to be implemented?

    There are a lot of companies that want to check their services, and implement extra token information that needs to be created with a username and password. Like Keycloak for instance.

    How long have you been using this project?

    2 months

    Additional information

    No response

    feature 
    opened by Oscar-Ruiz-R-Mojix 4
Releases(v4.2.0)
  • v4.2.0(Sep 16, 2022)

    • feat: Add [DOMAIN_EXPIRATION] placeholder for monitoring domain expiration using WHOIS https://github.com/TwiN/gatus/pull/325 - @TwiN
    • feat(alerting): Add client config for telegram https://github.com/TwiN/gatus/pull/324 - @lschloetterer
    • ux: Improve endpoint validation by checking type on start https://github.com/TwiN/gatus/pull/323 - @TwiN

    Full Changelog: https://github.com/TwiN/gatus/compare/v4.1.0...v4.2.0

    Source code(tar.gz)
    Source code(zip)
  • v4.1.0(Aug 22, 2022)

    • feat(alerting): Add Matrix alert provider #299 - @Kalissaac
    • feat(api): Configurable response time badge thresholds #309 - @Jesibu
    • feat(storage): Add optional write-through cache to sql store #315 - @TwiN
    • feat(remote): Implement lazy distributed feature #307 (EXPERIMENTAL) - @TwiN
    • refactor(storage): Remove decommissioned path for memory store #313 - @TwiN
    • ui(event): Add divider between each event - @TwiN

    Full Changelog: https://github.com/TwiN/gatus/compare/v4.0.0...v4.1.0

    Source code(tar.gz)
    Source code(zip)
  • v4.0.0(Jun 21, 2022)

    • feat(api)!: Remove deprecated paths - @TwiN
    • feat(storage)!: Remove deprecated persistence for memory storage - @TwiN
    • feat(security)!: Remove deprecated SHA512 parameter for password hashing - @TwiN
    • feat(alerting): Add group-specific WebHook URL for Google Chat #272 - @appleboy
    • feat(alerting): Add group-specific WebHook URL for Slack #279 - @mani9223-oss
    • feat(alerting): Add ENDPOINT_GROUP and ENDPOINT_URL placeholders for custom provider #282 - @TwiN
    • feat(alerting): Add overrides for Mattermost #292 - @mindcrime-ilab
    • feat(metrics): Add more metrics #278 - @wei840222
    • feat(client): Added client configuration option for using a custom DNS resolver #284 - @tiwood
    • feat(ux): Display loading animation while waiting for data to be retrieved #289 - @TwiN
    • feat(ui): Implement parameter to hide URL from results #294 - @asymness
    • feat(badge): Implement UP/DOWN status badge #291 - @asymness
    • fix(ui): Set default refresh interval to 300 (5m) - @TwiN
    Source code(tar.gz)
    Source code(zip)
  • v3.8.0(Apr 26, 2022)

    • feat(alerting): Add group-specific webhook URL for Teams #266 - @appleboy
    • feat(alerting): Add group-specific webhook URL for Discord #271 - @appleboy
    • feat(ui): Add support for buttons below header #106 - @TwiN
    • chore: Update Go to 1.18 - @TwiN
    • chore: Update frontend dependencies - @TwiN
    Source code(tar.gz)
    Source code(zip)
  • v3.7.0(Mar 23, 2022)

    • feat(alerting): Add support for custom Telegram API URL #257 - @jon4hz
    • feat(alerting): Add group-specific configuration to email provider #264 - @appleboy
    • feat(client): OAuth2 Client credential support #259 - @tiwood
    • fix(config): Replace hostname in error string if opted #262 - @shashank68
    • security: Pin front-end dependency versions - @TwiN
    Source code(tar.gz)
    Source code(zip)
  • v3.6.0(Feb 6, 2022)

    • feat(alerting): Added Google Chat alerting provider #234 - @kpolischuk
    • feat(alerting): Allow specifying a different username for email provider #231 - @tmoitie
    • fix(ui): Prettified event timestamps #243 - @TwiN
    • style(ui): Improved login UI design - @TwiN
    • build(docker): Support more platforms for latest tag #238 - @kkhan01
    • chore: Updated front-end dependencies - @TwiN
    • chore: Fixed a few typos in the documentation #241 - @ItsAzaria
    Source code(tar.gz)
    Source code(zip)
  • v3.5.0(Jan 9, 2022)

    • feat(ui): Updated project logo - @TwiN
    • feat(ui): Status page headline and link to open when clicking on the logo can now be configured #232 - @TwiN
    • feat(security): Added support for OpenID Connect #228 - @TwiN
    • feat(security): Implemented security.basic.password-bcrypt-base64 in favor of security.basic.password-sha512 #233 - @TwiN
    • feat(alerting): Added Opsgenie alerting provider #214 - @vinicius73
    • feat(metrics)!: Updated metrics exposed #223 - @TwiN
    • fix(alerting): Added group in alert messages #221 - @TwiN
    • fix: Improved endpoint and alert validation #221 - @TwiN
    • refactor: Moved from io/ioutil to io and os packages #211 - @Juneezee
    • docs: Fixed several typos #215 #216 #217 - @ianagbip1oti
    • docs: Added missing maintenance configuration in main configuration table #226 - @zeylos
    • perf: Replaced GitHub's PNG logo for a SVG - @TwiN
    • style: Default to dark mode - @TwiN
    Source code(tar.gz)
    Source code(zip)
  • v3.4.0(Dec 3, 2021)

  • v3.3.6(Nov 18, 2021)

  • v3.3.5(Nov 17, 2021)

  • v3.3.4(Nov 17, 2021)

    • Events now display the number of days ago rather than the number of hours if the event happened more than 72 hours
    • Fixed icon_url for Mattermost alerts
    • Updated TwiN/health to v1.1.0
    • Updated front-end dependencies
    Source code(tar.gz)
    Source code(zip)
  • v3.3.3(Nov 6, 2021)

    • Deprecated storage.file in favor of storage.path #197
    • Deprecated persistence for storage of type memory #198
    • Minor data savings improvement
    Source code(tar.gz)
    Source code(zip)
  • v3.3.2(Oct 29, 2021)

  • v3.3.1(Oct 25, 2021)

  • v3.3.0(Oct 23, 2021)

    Renamed service to endpoint #191 #192

    THIS CHANGE IS BACKWARD COMPATIBLE

    I've been wanting to rename service to endpoint for a while now. service is confusing, and it doesn't align well with features I want to implement in the future.

    As such, I finally decided to make the move.

    What you need to know

    For most people, all you need to do is replace services: by endpoints: in your configuration file, but here's a full break down of the changes that may impact you.

    Endpoint changes

    All /api/v1/services/* routes will continue working until v4.0.0 for the sake of backward compatibility, but should be replaced by /api/v1/endpoints/*.

    This includes badges.

    Configuration changes

    services has been renamed to endpoints, but the former will continue being supported until v5.0.0. This is a pretty big breaking change, and I want people to have enough time to migrate.

    Before:

    services:
      - name: website
        url: "https://twin.sh/health"
        conditions:
          - "[STATUS] == 200"
    

    After:

    endpoints:
      - name: website
        url: "https://twin.sh/health"
        conditions:
          - "[STATUS] == 200"
    

    If you continue using services in your configuration, there will be a warning logged in the console pointing to this issue

    Storage

    SQLite and Postgres

    If you are using a storage of type sqlite or postgres, the data in the old tables will not be migrated. I considered automatically migrating the data, but decided that it was not worth the trouble given that currently, the retention period is very short.

    That being said, the old tables are not going to be automatically deleted, in case you are using said data for other purposes.

    Here is a list of the old table names and their replacements:

    • service -> endpoints
    • service_event -> endpoint_events
    • service_result -> endpoint_results
    • service_result_condition -> endpoint_result_conditions
    • service_uptime -> endpoint_uptimes

    If you have any questions, please ask them in https://github.com/TwiN/gatus/issues/191

    Source code(tar.gz)
    Source code(zip)
  • v3.2.3(Oct 18, 2021)

  • v3.2.2(Oct 8, 2021)

  • v3.2.1(Oct 4, 2021)

    • Updated Go to 1.17
    • Added /v3 to module path: Gatus was never meant to be used as a library, but I have a use case for this now, hence the small release.
    Source code(tar.gz)
    Source code(zip)
  • v3.2.0(Oct 3, 2021)

    • Added support for maintenance window #74
    • Added optional services[].enabled parameter #175 - Thanks to @1newsr
    • Added support for monitoring endpoints via TLS #177 - Thanks to @Carlotronics
    Source code(tar.gz)
    Source code(zip)
  • v3.1.0(Sep 15, 2021)

  • v3.0.0(Sep 6, 2021)

    Breaking changes

    • Kubernetes auto discovery has been removed #135
    • service[].insecure has been replaced in favor of service[].client.insecure
    • alerting.mattermost.insecure has been replaced by alerting.mattermost.client.insecure
    • alerting.custom.insecure has been replaced by alerting.custom.client.insecure

    The following deprecated endpoints have been removed:

    • /api/v1/statuses
      • Replaced by /api/v1/services/statuses
    • /api/v1/statuses/{key}
      • Replaced by /api/v1/services/{key}/statuses
    • /api/v1/badges/uptime/{duration}/{identifier}
      • Replaced by /api/v1/services/{key}/uptimes/{duration}/badge.svg

    Features

    • Added the ability to hide the hostname of a service #159
    Source code(tar.gz)
    Source code(zip)
  • v2.9.0(Aug 22, 2021)

    • Added badges for response time #160 #156
    • Added a response time chart #160 #142
    • Updated badge colors #125
    • Created new endpoints:
      • /api/v1/services/statuses
      • /api/v1/services/{key}/statuses
      • /api/v1/services/{key}/uptimes/{duration}/badge.svg
      • /api/v1/services/{key}/response-times/{duration}/badge.svg
      • /api/v1/services/{key}/response-times/{duration}/chart.svg
    • Deprecated the following endpoints:
      • /api/v1/statuses
      • /api/v1/statuses/{key}
      • /api/v1/badges/uptime/{duration}/{identifier}

    NOTE: This major release may be the last one before v3.0.0. If you're using any of the deprecated endpoints or configuration parameters, make sure to migrate to them as soon as you can.

    Source code(tar.gz)
    Source code(zip)
  • v2.8.2(Aug 15, 2021)

    • Renamed storage type inmemory to memory
    • Added more uptime badge colors #125

    NOTICE: v3.0.0 is just around the corner, and with it will come several breaking changes. For those of you using the latest tag, you may want to pin a specific version. Furthermore, keep an eye on the startup application logs, as most deprecated features your configuration is still leveraging that will be removed or modified in v3.0.0 should have relevant logs warning you of what to expect.

    Source code(tar.gz)
    Source code(zip)
  • v2.8.1(Jul 30, 2021)

    • Added alerting provider for Microsoft Teams #143 - Thanks to @zeylos
    • Added the ability to configure the client used to monitor services (timeout, insecure, ignore-redirect) and some alerting providers #126
      • Deprecated alerting.custom.insecure in favor of alerting.custom.client.insecure
      • Deprecated alerting.mattermost.insecure in favor of alerting.mattermost.client.insecure
    • Deprecated Kubernetes implementation (see discussion)
    Source code(tar.gz)
    Source code(zip)
  • v2.8.0(Jul 28, 2021)

    • Added support for persistence with SQLite #136
    • Added documentation about deployment using a Helm chart #127
    • Added documentation about deployment using Terraform
    • Fixed issue with ICMP not working on macOS #132
    • Fixed issue with Gatus following redirects by default #126
    Source code(tar.gz)
    Source code(zip)
  • v2.7.0(Jun 18, 2021)

    • Added support for StartTLS protocol - Thanks to @gopher-johns #120
    • Fixed an issue with partially invalid JSONPath not returning an error #122
    • Errors are no longer duplicated #123
    • Fixed UI issue with settings bar
    Source code(tar.gz)
    Source code(zip)
  • v2.6.0(May 28, 2021)

    • Implemented automatic reload on configuration file update #29 #115
    • Implemented default provider alert #91
    • No longer explicitly targeting IPv4 for ICMP service checks #111 #113
    Source code(tar.gz)
    Source code(zip)
  • v2.5.0(May 11, 2021)

    • Implemented dark theme #99
    • Fixed JSONPath parsing issue not working when [BODY] was an array #107
    • Restructured uptime metrics (backward compatible + auto migration)
    • Minor visual improvements and fixes
    Source code(tar.gz)
    Source code(zip)
  • v2.4.0(Apr 5, 2021)

    • Added support for Telegram alerting provider - Thanks to @jon4hz #102
    • Long strings are now truncated when using pattern function - Thanks to @dchidell #100
    • Added toggleable average response time (frontend)
    • Refresh interval is now persisted through sessionStorage (frontend)
    • Updated Go to 1.16
    Source code(tar.gz)
    Source code(zip)
  • v2.3.0(Mar 13, 2021)

    • Added Discord alerting provider #48
    • Added has() function to determine if an element at a given JSONPath exists
    • Reduced overall memory usage
    • Significant performance improvement
    • Significantly improved uptime calculation

    Note: If you were using persistence in v2.2.0 or earlier, upgrading to v2.3.0 will cause the loss of uptime statistics (1h, 24h, 7d). This is due to a rewrite of the way the uptime history is computed and persisted. This was needed for the future implementation of a long term uptime history. No actions are required on your end.

    Source code(tar.gz)
    Source code(zip)
Owner
Chris C.
I love programming
Chris C.
An simple, easily extensible and concurrent health-check library for Go services

Healthcheck A simple and extensible RESTful Healthcheck API implementation for Go services. Health provides an http.Handlefunc for use as a healthchec

Ether Labs 234 Sep 27, 2022
Track health of various dependencies - golang

Background This package helps setup health check based on status of external dependencies. The idea is to add all external dependencies like database,

Dave Amit 1 Dec 17, 2021
A Simple HTTP health checker for golang

patsch Permanently Assert Target Succeeds Check Health use cases used by kubernetes cluster admins to quickly identify faulty ingresses used by kubern

DB Schenker 4 Feb 22, 2022
Render health ECG (electrocardiogram) animation

HealthECG Render health ECG (electrocardiogram) animation About This program shows how the health ECG animation was implemented in the original Reside

null 0 Jan 6, 2022
🌍 📋 A web dashboard to inspect Terraform States

?? ?? A web dashboard to inspect Terraform States

Camptocamp 1.6k Sep 27, 2022
A small web dashboard with stats for all pipelines of Buildkite organization.

Buildkite Stats A small Buildkite dashboard useful to prioritize which pipelines a Buildkite organization is waiting the most on. Noteworthy details:

Jens Rantil 1 Apr 25, 2022
This Simple script is used to convert Datadog Dashboard to NewRelic.

What is this? This Simple script is used to convert Datadog Dashboard to NewRelic. This script is build with specific dashboard layout in mind, so it

null 4 Feb 6, 2022
HTTP service to generate PDF from Json requests

pdfgen HTTP service to generate PDF from Json requests Install and run The recommended method is to use the docker container by mounting your template

Hyperboloide 60 Sep 27, 2022
Kratos Service Layout

Kratos Layout Install Kratos

Kratos 257 Sep 22, 2022
An HTTP service for customizing import path of your Go packages.

Go Packages A self-host HTTP service that allow customizing your Go package import paths. Features Reports. Badges. I18N. Preview I launch up a free H

Razon Yang 18 Nov 18, 2021
A service for predicting the order of keys to use for opening doors in Ladder Slasher

A service for predicting the order of keys to use for opening doors in Ladder Slasher.

Jason Simmons 0 Oct 29, 2021
Service for firewalling graphite metrics

hadrianus Block incoming graphite metrics if they come in too fast for downstream carbon-relay/carbon-cache to handle. Building Hadrianus is written i

Kambi 7 Apr 28, 2022
Example hello-world service uses go-fx-grpc-starter boilerplate code

About Example hello-world service uses https://github.com/srlk/go-fx-grpc-starter boilerplate code. Implementation A hello world grpc service is creat

null 0 Nov 14, 2021
Typesafe lazy instantiation to improve service start time

Package lazy is a light wrapper around sync.Once providing support for return values. It removes the burden of capturing return values via closures from the caller.

Jeremy Loy 1 May 30, 2022
Implement a toy in-memory store information service for a delivery company

Implement a toy in-memory store information service for a delivery company

Ahmad Berahman 0 Nov 22, 2021
An in-memory, key-value store HTTP API service

This is an in-memory key-value store HTTP API service, with the following endpoints: /get/{key} : GET method. Returns the value of a previously set ke

Ujjwal Goyal 1 May 23, 2022
A Simple Bank Web Service implemented in Go, HTTP & GRPC, PostgreSQL, Docker, Kubernetes, GitHub Actions CI

simple-bank Based on this Backend Master Class by TECH SCHOOL: https://youtube.com/playlist?list=PLy_6D98if3ULEtXtNSY_2qN21VCKgoQAE Requirements Insta

Tien La 0 Dec 9, 2021
Golang service boilerplate using best practices

go-boilerplate Golang service boilerplate using best practices. Responsibility: Register (CRUD) and Login Users with JWT. Dependencies Gin-Gonic Swagg

Filipe Alves 10 May 11, 2022
The Bhojpur BSS is a software-as-a-service product used as an Business Support System based on Bhojpur.NET Platform for application delivery.

Bhojpur BSS - Business Support System The Bhojpur BSS is a software-as-a-service product used as an Business Support System based on Bhojpur.NET Platf

Bhojpur Consulting 0 Sep 9, 2022