GitXplorerGitXplorer
M

checkupapi

public
1 stars
0 forks
0 issues

Commits

List of commits on branch master.
Unverified
def2d3db9abbccfb0920aeafc3422b02bee7685f

Minor README update

MMcKael committed 7 years ago
Unverified
9a23791059fc67a75dce0d0fe6070f0483a58a0c

Add sample status page

MMcKael committed 7 years ago
Unverified
63ce0c1ac8717baba2132f61c946676a83b52dab

Update README

MMcKael committed 7 years ago
Unverified
00fc63686511cc3a80b1e4e33008c0101b20e62a

Fix link to the API specifications

MMcKael committed 7 years ago
Unverified
72578e23d4ac83db5b0fcdd4f33410a24961380d

Add Travis file

MMcKael committed 7 years ago
Unverified
fad51271ef50e73352a12d74a55d9543e6a1ab65

Add (MIT) license and README files

MMcKael committed 7 years ago

README

The README file for this repository.

CheckupAPI

API server for Sourcegraph checkup data

godoc license build Go Report Card

checkupapi is a Go REST API to access data generated by checkup.

Purpose

The goal of checkupapi is to provide a common and efficient interface to read checkup's data without knowledge about checkup storage. Currently, the supported checkup storages are those that implement the StorageReader interface (FS, SQL and Github -- the Github backend has not been tested).

With checkupapi, getting an event timeline or statistics is very fast and does not require a heavy CPU load on the client side.

Please check the API specifications for more details.

Installation

You can install the API server with the go command line tool:

% go get github.com/McKael/checkupapi

and ugrade it with

% go get -u github.com/McKael/checkupapi

Usage

checkupapi can use the same configuration file as checkup.

The default port is 8801, you can change it with the --http command line flag.

E.g.:

% checkupapi -c /etc/checkup/checkup.json --http :8080

You can then query the API (see the API endpoints):

% curl localhost:8080/api/v1/check
OK      2017-08-26 10:25:06 +0200 CEST

Sample web status page

A status page, derived from checkup's one, has been included.

Instead of fetching results from checkup storage it does query the API to get event timeline and statistics. The API URL must be set in js/config-api.js.

References