/adminshould not be necessary. Are you saying you couldn't get invite working without /admin? @mikkeschiren
SELECT strip(jsonb_to_tsvector('english', jsonb_agg(data), '["string"]')) FROM (SELECT events_event.data from events_event where issue_id = x limit 1000) as data;
ERROR: total size of jsonb array elements exceeds the maximum of 268435455 bytesand
string is too long for tsvector (1101146 bytes, max 1048575 bytes)and is potentially slow.
I haven't tested discord, do you think you could open an issue on gitlab and ideally a merge request with a failing unit test?
Webhooks use the slack-like message syntax. So if an app doesn't support it, then it won't work.
I'm making a handy new tool
./manage.py ingest_benchmark 0.8869080519998533
The idea is to very quickly benchmark. It's probably not as good as using locust for load testing on a real server, but it's fast and easy to run on different branches and compare.
My glitchtip/glitchtip-backend!80 that moves some event processing into celery has exactly the results I would expect.
Must faster event processing in the web request, almost twice as fast.
Lower overall processing likely due to redis/celery overhead and a need for additional queries.
I'm currently working on implementing uptime monitoring on GlitchTip's frontend (at the moment it is only available from the administrative backend). Trying to come up with some help text for the various types of monitors we offer. What does everyone think of these descriptions?
Ping: GlitchTip will "ping" the specified URL using an HTTP HEAD request with no payload.
GET: GlitchTip will send an HTTP GET request to the specified URL.
POST: GlitchTip will send an HTTP POST request to the specified URL.
Heartbeat: GlitchTip will await requests from your site to ensure it is active.