Maybe Heartbeat: GlitchTip will await requests from your site to ensure it is active. If it doesn't receive the request, it will be marked as Down.
for any spectators, the monitoring code is very easy to follow actually https://gitlab.com/glitchtip/glitchtip-backend/-/blob/master/glitchtip/uptime/utils.py#L35
well...easy to read if you know how async python works :P and probably fine if you don't.
I would offer 1 year of our hosted small plan for anyone willing to try out uptime monitoring in realistic scenarios and tell us what you think about it and how notifications should work.
(or stickers)
Hello, GlitchTip community! This newbie is facing a conundrum right now and need your help making GlitchTip work.
I'm running GlitchTip using the Docker image (v1.8.5) and deployed it on top of Azure WebApp. It's running, I can manage stuff (create organization, etc.) I'm having a problem with adding users. The invite doesn't work (user get's added but pending), email doesn't get sent. I did have EMAIL_URL added as an Azure environment variable (smtp+ssl:// ) using Sendgrid. The credentials used are working in another tool (Saleor), but it's just not working on GlitchTip. GlitchTip log is also spewing 409 error whenever I attempt to invite a new user. Help?
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.
1 reply
Exclusive gitter offer of the day - free stickers and/or free small plan months for app.glitchtip.com for anyone who is willing to DM me how they found GlitchTip and why they would or wouldn't pay for support/hosting. I'm looking for people who use it for a company. The stickers are the glitchtip logo and characters on glitchtip.com https://glitchtip.com/assets/home/bots-assembled@2x.webp
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.
No real way to filter that without going through a many to many field which causes the duplicates
Researching OSS Sentry more, it seems like teams don't actually filter issues as I thought they would. Which sounds unintuitive to me. A user in 0 teams will see 0 projects. But can see every event and issue.
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.
@james.kiger_gitlab can you validate my thinking a little here
I can't find any authoritative docs on this. OSS Sentry's lower membership role is "member" which says "Members can view and act on events, as well as view most other data within the organization." Taken literally I suppose one could say that means they can view and act on all events. And the UI supports it pretty well. I can view an issue but I can't see the project details. Presumably this is intended behavior.
old issue here getsentry/sentry#1296 "Organization Members will supercede Team Members"
so I'm leaning towards solving this by adjust documentation to be REAL clear that team membership doesn't affect permissions in any way. It's more of a workflow for notifications and issue workflow.
So one question is where we want to put this documentation. On the organization side, it's easy enough since there is an invite member page. On the team side it's a little trickier, since there isn't an "invite team member" page. Members are added to teams directly from the list of team members.
can you show me a screenshot of that? Where a user encounters teams
gitter ui might be more limited
/org-slug/settings/teams/ would be the main page for teams and a reasonable place to add text
but a user might be able to avoid that page since it's referenced elsehwere
Yeah, and since it's a list if we put it at the bottom and they have a lot of teams they might never see it
my vote - add a sentence to Create a New Team modal. Then add maybe 2-3 sentences to settings/teams
It needs to convey that teams about about notifications and workflow. Organizations manage permissions.
I still think that's really dumb but not an issue we can easily tackle if we aim for api compat
Does that surprise anyone else in the community? That a org member who isn't in a team, can see all issues in said team.
"GlitchTip teams are for managing event notifications. View permissions are handled through organization membership."
but even the lowest role "member" can view all issues
or is supposed to be able to :P in GT today they can't but we're talking about "fixing" that
organization membership
That could be a link that opens in a new tab
"GlitchTip teams are for managing issue notifications and workflow."
For the "invite member" page:
:Organization member status grants view access to all of an organization’s events handled by GlitchTip."
:Organization member status grants view access to all of an organization’s events handled by GlitchTip."
I know "workflow" is ambiguous, but it does/should have have subtle effects in the UI