by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
KaKi87
@KaKi87
It also supports JSON.
David Burke
@bufke_gitlab
Can you tell me a little about your use case? Just to make sure I don't miss some important context?
KaKi87
@KaKi87
Well, I was using sentry/onpremise 20.x, not 9.x, because we want to use a software that is up to date.
Here are my two main use cases :
  • In Vue.JS, we send the content of the vuex store (localStorage)
  • In Azure Functions, we send the context object (somewhat similar to an Express.JS request object)
David Burke
@bufke_gitlab
And then you just look it up in the interface and read that context right? Do you search or filter on that data?
KaKi87
@KaKi87
For the few days I've been using Sentry I only looked it up in the interface and read it.
Search would be useful but not vital for now.
David Burke
@bufke_gitlab
Basic search would work automatically (because we index the entire json document) but our full text search is still pretty basic compared to Sentry
KaKi87
@KaKi87
Also I use the setUser method additionally to setExtra, and both in JS, Node, Java and Objective C.
David Burke
@bufke_gitlab
I don't think this would take long at all to support. Instead of sending you a quote as a Burke Software project, how about I just implement this and if you like it - you can donate whatever amount you feel is appropriate here https://liberapay.com/GlitchTip/donate
KaKi87
@KaKi87
Absolutely.
David Burke
@bufke_gitlab
ok, I'll post updates here. I'll work on it tonight and get it in the next release (later this week)
KaKi87
@KaKi87
Thank you very much, as a fellow FLOSS developer I understand how hard it can be to handle user priorities so I'll make sure you'll be generously compensated.
Also, I'd like to ask you about two other features : Vue.JS source map support, and SSO through self-hosted GitLab CE ? Those are non-vital though. Thanks again.
KaKi87
@KaKi87
Actually there's something else : I tried to disable registration using ENABLE_OPEN_USER_REGISTRATION = false in docker-compose.yml (as per glitchtip/glitchtip-backend!21) but Docker said that false [...] is an invalid type ??
Brendan Berkley
@BrendanBerkley_gitlab
don't remember offhand, but did you try either False or "false" ?
KaKi87
@KaKi87
You mean I should use false as a string, not a boolean ?
Brendan Berkley
@BrendanBerkley_gitlab
I think so.
KaKi87
@KaKi87
Feels weird, but it worked indeed. Thanks
Alex Hathaway
@ahathaway
@bufke_gitlab @KaKi87 i am also interested in context support. I plan to use glitch across several environments, dev/stage/prod and setting these values in context would be very helpful
KaKi87
@KaKi87
Actually, there's another Sentry feature for versionning support, which is more adapted to your situation
Alex Hathaway
@ahathaway
Oh? Please share
i am just now learning about all of the features of sentry sdk. I am using both nodejs and php versions.
Alex Hathaway
@ahathaway
ahhh ok
Thanks!
KaKi87
@KaKi87
You're welcome !
Alex Hathaway
@ahathaway
I am also interested in context for tracking active user and other info as well, however this releases is ideal for environments. @bufke_gitlab does glitch already support releases?
KaKi87
@KaKi87
@bufke_gitlab I actually have another vital feature to request : comments. Thanks
David Burke
@bufke_gitlab
booleans: Those are environment variables which are always strings. My understanding is that django-environ will parse both "False" and "false" as False.
I've used Sentry before they has a SaaS version and I'm learning they had new features I never used before all the time :)
Environments and releases are on my radar. Storing and filtering the information wouldn't be too hard. There are some more advanced features such as using releases to mark when a regression takes place that probably wouldn't get done any time soon. We're working on a roadmap to help explain what's supported vs not.
Alex Hathaway
@ahathaway
@bufke_gitlab yeah i think for now just a simple tag in the UI showing as a result of context or releases so that someone doesnt need an install of glitch for each environment is all im looking for currently. Also being able to tie events/issues to context (such as the logged in user) would also be helpful for our use case and closing the feedback loop from our customers reporting to our support team. The whole “can you try to reproduce the error” with an end user is sometimes fruitless and i feel like supporting context would be very helpful for this.
KaKi87
@KaKi87
Question : is there a particular reason why you started a new software from scratch instead of just forking and continuing the development of open source Sentry from v9 ?
David Burke
@bufke_gitlab
We evaluated a fork vs reimplementation - notes are here glitchtip/meta#9
David Durieux
@ddurieux
\o/
David Burke
@bufke_gitlab
btw user and extra context draft is here glitchtip/glitchtip-backend!36
as you can see the tests fail, which is a good thing :) once that is finished I need to add it to the frontend
KaKi87
@KaKi87
Well, after re-evaluating my needs, I noticed that this new software you started from scratch is actually lacking of tons of frontend features that I really miss. So I made my own backend reimplementation, for now only tested with the VueJS & NodeJS SDKs, to generate git issues (only Gitea for now) at each event (or as a comment for existing events). The main advantage of my idea is that no frontend nor database is required as the git repository hoster already fullfill that role. Here's what I've come up with in a day. https://git.kaki87.net/KaKi87/glitchgit

David Burke
@bufke_gitlab
if a solution is simple and it works for you - then it sounds like a great solution. The problem space around GlitchTip includes dealing with having 1 million events around 1 issue. And things like full text search and analytics. So I don't think a git backend would work for us here.
KaKi87
@KaKi87
I understand. Personally I wouldn't ever host a database this big myself even if the server is supposed to handle it anyway :sweat_smile: Regarding analytics, I'm absolutely not interested. The only thing I'm into is getting and fixing errors before the user has to report these.
Alex Hathaway
@ahathaway
@bufke_gitlab can confirm your fixes for the php sdk worked. My application is now reporting errors properly again to glitchtip. Thanks!
David Burke
@bufke_gitlab
:thumbsup:
David Burke
@bufke_gitlab
Event context and user data are now merged into the backend
Alex Hathaway
@ahathaway
@bufke_gitlab Yay!!! xmas coming early this year!
David Burke
@bufke_gitlab
Notifications UI is finally done! This will mark our 1.1 release. ETA is Tuesday. Soon you'll be able to configure email notifications without Django admin - which will be a big feature for app.glitchtip.com users.
Random things I'm thinking about
  • Does anyone want to run without redis/celery? Because it's feasible for smaller installations but not supported.
  • Does anyone want GlitchTip via a deb, flatpak, or snap? I say this as an avid Linux enthusiast, but it's quite painful to support them all as a developer. What do people who don't like using Docker want? I believe there are more than a few said folks.
  • We'll be doing 1.2 planning soon - so submit/upvote issues on gitlab now for feature requests https://gitlab.com/groups/glitchtip/-/issues
David Durieux
@ddurieux
cool
Alex Hathaway
@ahathaway
@bufke_gitlab was trying to figure out which version of the sentry php sdk you developed against? Was going to version lock my composer dependencies to that for now.
David Burke
@bufke_gitlab
It should be safe to use the latest.
David Burke
@bufke_gitlab
1.1 is live
Emily Jensen
@emilyjensen_gitlab
I created a notifications UI, so you can set how often alerts are sent for each project (in project settings) and chose what projects you would like to receive alerts for in your profile!