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.
The top of this page has a quick python test to check email https://docs.djangoproject.com/en/3.2/topics/email/
Email uses django-environ. We also offer paid installation help if desired.
This issue is tripping me up today glitchtip/glitchtip-backend#109
The query needs a distinct but the performance impact is not even worth considering (start counting query time in minutes)
Sentry OSS doesn't help because they simply omit the ability to search issues without setting and organization which greatly simplifies the problem. Could do the same....I was dreaming one day to have a homepage that isn't org specific but that probably isn't all that important.
That sounds .... like a security vulnerability? You add new employee to the org. You ensure new employee is not in the devops team. You submit event data with confidential data to the devops project. You expect new employee not to be able to read said confidential data but they can actually.
I'm even more confused.
/org-slug/settings/teams/would be the main page for teams and a reasonable place to add text
That could be a link that opens in a new tab