Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
David Burke
@bufke_gitlab
I do want GlitchTip to be very easy to run even on smaller instances and smaller budgets. I think that's one area we can be very competitive with Sentry.
Alex Hathaway
@ahathaway
Ok, I will investigate a bit more as time permits. I think part of what I might be dealing with an IOPS issue using the root device on the instance, I was going to try and provision another EBS volume with a higher IOPS to see if that helps w/ running PG in a container as well.
AWS specific here if that wasn't apparent. ;)
adamgogogo
@adamgogogo
Hi, guys, my question is which category should I keep in docker for persistence data? Thanks very much!
David Burke
@bufke_gitlab

Are you asking if it's a good idea to keep persistent data in docker and if so, what data?

I don't think there's a right answer to that. Personally, I prefer not to keep any persistent data in Docker and Kubernetes because in my experience persistent data is hard to keep highly available. I prefer to use managed databases like RDS or DigitalOcean's managed databases. I would say use what you are most comfortable with. If you don't mind working with docker and have a smaller instance using docker-compose then you're probably fine with that.

The only persistent data in GlitchTip is in Postgresql.

adamgogogo
@adamgogogo
ya,
I mean outside the docker, thanks a lot! pgsql is what I want~^^
David Burke
@bufke_gitlab
Gitlab supports generic packages now and attaching them to a release. If anyone wants a tar.gz distribution of the complete django+JS app open an issue about it. I have no personal interest but it's easier to do now.
it would just be the django app - the admin would still be responsible for setting up a server like nginx.
could probably support other deploy options too - just open an issue or upvote existing ones. I'll support what the most people want.
David Burke
@bufke_gitlab
@G4brym I'm working on releases right now. It should be present (at least for your needs) in GlitchTip 1.3. If you set the release in the sentry client SDK it will save to GlitchTip. The more advanced features such as "mark resolved in next release" won't be supported yet.
Gabriel Massadas
@G4brym
That's great, theses advanced features aren't really a priority, the support for release is already very good :)
Thanks a lot!
My merg request doesn't make sense any more, i will close it
Do you guys have any roadmap? maybe i can help on some smaller issues first
David Burke
@bufke_gitlab
We have gitlab issues including features we want https://gitlab.com/groups/glitchtip/-/issues
Starter contribution ideas:
  • Create or update a "error factory" which is just a small problem demonstrating some errors with the sentry SDK https://gitlab.com/glitchtip/error-factories
  • Update documentation
  • Add more release related features. Any API field in sentry OSS could be added to Glitchtip
  • Webhook support
David Burke
@bufke_gitlab
I'm working on performance monitoring - we should have a very preliminary version up on the next release. Mostly it's helping me think about longer term data modeling. If you have a specific need for monitoring let me know. I could use a couple small use cases to prioritize first. My best guess is just a sortable list of transactions that lets you see the what your slowest requests are (and maybe read some json if you want more info). Uptime monitoring is still on my mind too because I think it's a great use case for GlitchTip and fits into the existing Event model.
David Burke
@bufke_gitlab
We're also looking for a freelance illustrator for branding needs. Email info@burkesoftware.com with portfolio examples if you know anyone.
Amantel
@Amantel
Hey, hey, community!
Is this a place to ask 'wow, I don't get how to use it' questions?
Hm... judging from the last message date, the answer is probably no :)
Brendan Berkley
@BrendanBerkley_gitlab
hello!
What questions do you have?
Amantel
@Amantel
Basically I can't set any tags
According to sentry API docs that should be pretty easy, but with withScope or with configureScope (or with combination of them), I can't see any tags I set in the UI. I can see them in the JSON, though
```
function: "null.<anonymous>",
pre_context: [
"});",
"",
"Sentry.withScope((scope) => {",
" scope.setTag('error-type', 'soft_error');",
" scope.setTag('aaaa', 'bbb');",
"",
" scope.setLevel('warning');"
],
context_line: " Sentry.captureException(new Error('Test'));",
```
After googling around and lurking on SOF I am not very sure how to proceed
(btw, it is NodeJS setup)
David Burke
@bufke_gitlab

There's support for tags, but I'm not sure if it works with this scope thing. I never used scopes and I made the backend so the answer is probably no :)

Assuming the sentry SDK just sends these tags to the backend, it should be trivial to support. I'll confirm this tonight and open an issue. If you're interested in paid support I'd be happy to expedite this feature too and make sure we can get it working for you @Amantel .

Amantel
@Amantel
Thanks, David!
While we are exploring the situation with scope, can you point out how I can send tags? TBH, I do not want to use scope or anything fancy. My goal is to tag a subset of errors / warning with er... tags.
David Burke
@bufke_gitlab

Brendan confirmed it glitchtip/meta#44

The only tags that are supported are ones created server side like Device, browser, etc. But since we already have a system for tags, it should be easy to add client sent tags. I expect this feature for our next release - 1.3

Amantel
@Amantel
Excellent! Thanks!
Amantel
@Amantel
BTW, while we are at it, maybe you will consider the support for setLevel both in the 'event card' UI and in the list UI (e.g. allow use to filter out specific levels).
You have setLevel in your glitchtip/meta#44
dyarfaradj
@dyarfaradj
I just added a new feature request: glitchtip/meta#45
Brendan Berkley
@BrendanBerkley_gitlab
Thanks for submitting!
dyarfaradj
@dyarfaradj
I honestly would love to contribute to the project with pr but as I've said previously I'm not familiar with Angular for the frontend and I don't have the time to sit into angular atm. Even tho my feature request is pretty easy to do in any language xD
Brendan Berkley
@BrendanBerkley_gitlab
Our 1.2 release was the first that had any kind of documentation for the SDK. We definitely need to make it more accessible moving forward.
dyarfaradj
@dyarfaradj
Ahh, alright. Yeah
David Burke
@bufke_gitlab
Always feel free to ping me or someone else if you want help contributing. Happy to discuss whatever when I have time.
David Burke
@bufke_gitlab
@Amantel client tag support is done. You'll need to wait till the 1.3 release to see it work. I'd estimate that landing in 1-2 weeks. You can run from git, but I don't recommend that for production.
We should cull 1.3 issues too - this is way too many. https://gitlab.com/groups/glitchtip/-/issues?milestone_title=1. I'm going to start pushing some back now.
Amantel
@Amantel
@bufke_gitlab great news!
A UI question - how can I delete / mark as resolved all (or 'a lot') of issues? I misjudged and now I have 1500+ issues I want to get rid off and I spent last 5 minutes going through pagination and selecting 50 at a time and that seems pretty dull. Is there 'select' all button somewhere?
David Burke
@bufke_gitlab

hmm yeah I opened an issue about that glitchtip/glitchtip-frontend#140

The only short term workaround I can think of is to use the API directly. Docs are autogenerated, but better than nothing https://app.glitchtip.com/docs/ also it mostly matches the sentry backend API, at least while it was open source.

Brendan Berkley
@BrendanBerkley_gitlab
I made a quick comment on that with two ideas for UI. @Amantel if you have any other ones feel free to upload a sketch or type something out
David Burke
@bufke_gitlab
backend is now good to perform bulk updates without specifying ids (which makes it apply them to the query)
Amantel
@Amantel
I like the gmail pattern (at least that was what I hoped to get). My big hope is that this will work well with tags from 1.3, e.g. will allow to delete some large subset of issues too.
David Burke
@bufke_gitlab
yeah it would work that way - it's the same code path as search/filter