mystiq/rageshake
Archived
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
No description
This repository has been archived on 2022-08-18. You can view files and clone it, but cannot push or open issues or pull requests.
64 commits 13 branches 8 tags 6.5 MiB
Go 93.3%
Shell 4.4%
HCL 1.2%
Dockerfile 1.1%
Find a file
Michael Kaye 4ce47beb7b Update go version to 1.16 
The linting scripts don't run on 1.15 any more, so builds are not
running against 1.15 any more.

Technically it will still compile and run against go 1.15 but if we
can't verify it in CI, it's not known to be true in future.
2022-01-18 18:13:03 +00:00
.buildkite Add support for creating GitLab issues (#37) 2021-08-10 18:04:58 +01:00
changelog.d add random string to report directories to prevent time-based collisions 2021-12-14 08:10:54 -05:00
hooks clean up lint scripts 2020-06-04 12:53:08 +01:00
scripts clean up lint scripts 2020-06-04 12:53:08 +01:00
.gitignore Rename sample config file 2017-04-12 15:27:50 +01:00
CHANGES.md 1.2 2020-09-16 11:35:38 +02:00
CONTRIBUTING.rst move CI to buildkite 2020-06-04 13:08:27 +01:00
Dockerfile Add Dockerfile 2019-08-29 09:07:08 +02:00
go.mod Add support for creating GitLab issues (#37) 2021-08-10 18:04:58 +01:00
go.sum Add support for creating GitLab issues (#37) 2021-08-10 18:04:58 +01:00
LICENSE Add readme, contributing, license 2017-04-04 16:20:50 +01:00
logserver.go move files to the source root 2019-04-10 12:22:44 +03:00
main.go add random string to report directories to prevent time-based collisions 2021-12-14 08:10:54 -05:00
rageshake.sample.yaml Add support for creating GitLab issues (#37) 2021-08-10 18:04:58 +01:00
README.md Update go version to 1.16 2022-01-18 18:13:03 +00:00
RELEASING.md fix thinkos in RELEASING.md 2020-06-05 09:33:50 +01:00
slack.go fix lint 2020-06-04 12:52:39 +01:00
submit.go add random string to report directories to prevent time-based collisions 2021-12-14 08:10:54 -05:00
submit_test.go move files to the source root 2019-04-10 12:22:44 +03:00
towncrier.toml 1.1 2020-06-04 13:15:38 +01:00

README.md

rageshake Build status

Web service which collects and serves bug reports.

rageshake requires Go version 1.16 or later.

To run it, do:

go build
./bin/rageshake

Optional parameters:

  • -config <path>: The path to a YAML config file; see rageshake.sample.yaml for more information.
  • -listen <address>: TCP network address to listen for HTTP requests on. Example: :9110.

HTTP endpoints

The following HTTP endpoints are exposed:

GET /api/listing/

Serves submitted bug reports. Protected by basic HTTP auth using the username/password provided in the environment. A browsable list, collated by report submission date and time.

POST /api/submit

Submission endpoint: this is where applications should send their reports.

The body of the request should be a multipart form-data submission, with the following form field names. (For backwards compatibility, it can also be a JSON object, but multipart is preferred as it allows more efficient transfer of the logs.)

  • text: A textual description of the problem. Included in the details.log.gz file.

  • user_agent: Application user-agent. Included in the details.log.gz file.

  • app: Identifier for the application (eg 'riot-web'). Should correspond to a mapping configured in the configuration file for github issue reporting to work.

  • version: Application version. Included in the details.log.gz file.

  • label: Label to attach to the github issue, and include in the details file.

    If using the JSON upload encoding, this should be encoded as a labels field, whose value should be a list of strings.

  • log: a log file, with lines separated by newline characters. Multiple log files can be included by including several log parts.

    If the log is uploaded with a filename name.ext, where name contains only alphanumerics, ., - or _, and ext is one of log or txt, then the file saved to disk is based on that. Otherwise, a suitable name is constructed.

    If using the JSON upload encoding, the request object should instead include a single logs field, which is an array of objects with the following fields:

    • id: textual identifier for the logs. Used as the filename, as above.
    • lines: log data. Newlines should be encoded as \n, as normal in JSON).

  • compressed-log: a gzipped logfile. Decompressed and then treated the same as log.

    Compressed logs are not supported for the JSON upload encoding.

  • file: an arbitrary file to attach to the report. Saved as-is to disk, and a link is added to the github issue. The filename must be in the format name.ext, where name contains only alphanumerics, - or _, and ext is one of jpg, png, or txt.

    Not supported for the JSON upload encoding.

  • Any other form field names are interpreted as arbitrary name/value strings to include in the details.log.gz file.

    If using the JSON upload encoding, this additional metadata should insted be encoded as a data field, whose value should be a JSON map. (Note that the values must be strings; numbers, objects and arrays will be rejected.)

The response (if successful) will be a JSON object with the following fields:

  • report_url: A URL where the user can track their bug report. Omitted if issue submission was disabled.

Notifications

You can get notifications when a new rageshake arrives on the server.

Currently this tool supports pushing notifications as GitHub issues in a repo, through a Slack webhook or by email, cf sample config file for how to configure them.