Package Details: sentry 9.1.2-1

Git Clone URL: https://aur.archlinux.org/sentry.git (read-only, click to copy)
Package Base: sentry
Description: Python-based realtime logging and aggregation server.
Upstream URL: http://pypi.python.org/pypi/sentry
Licenses: BSD
Submitter: zancarius
Maintainer: zancarius
Last Packager: zancarius
Votes: 14
Popularity: 0.000099
First Submitted: 2012-11-04 17:15
Last Updated: 2019-08-31 02:03

Pinned Comments

zancarius commented on 2020-01-23 21:38

I have spent some time exploring options for upgrading this PKGBUILD to the latest version of Sentry and have encountered blocking changes that do not appear to have a clear resolution.

Currently, there were two PKGBUILDs that provide our required Clickhouse dependency but neither of these build successfully. Near as I can tell, some of Clickhouse's upstream dependencies have known issues that as yet have no resolution outside attempting to patch either Clickhouse or wait for the upstream developers to address these deficiencies. This is not something either myself or the maintainer(s) of the Clickhouse PKGBUILD(s) can address (not easily, anyway).

Consequently, I will be updating this PKGBUILD, bumping the pkgrel in effort to increase the visibility of this issue. We will be holding Sentry at its current state until we have a clear path forward.

If you need Sentry 10.x.x in your environment, consider installing their official Docker packages. This is the currently recommended method for installing Sentry.

zancarius commented on 2020-01-17 06:45

Sentry v10.0.0 is out, but I will not be upgrading this package for some time. In fact, I'm not sure when an upgrade will be available because the number of additional service dependencies has since exploded.

To illustrate, Sentry v10.x now depends on:

  • Zookeeper
  • Kafka
  • Clickhouse
  • Snuba

I don't believe Snuba can be disabled in Sentry post-v9.1.2. If this is true, then this means that Sentry now has an implicit dependency on the JRE which may be prohibitive for those users who are running Sentry on lower end hardware or memory-constrained environments.

The official installation guide recommends installing the on-premise edition of Sentry via Docker and advises against source installation, which is what we're doing here.

This leaves us with a couple of options (plus a third thrown in as an either/or):

1) Upgrade anyway and add a host of other dependencies to the PKGBUILD that may surprise some users. Given that Sentry is a complex piece of software to install, this will only add to the complexity and will require additional packages, configuration, etc., that will need to be completed before Sentry can even be upgraded. (The migration process moves events from the database into Snuba, for example.)

2) Cheat and take the easy way out; deprecate this PKGBUILD and point users to the official Docker images. There's no point trying to wrap the Docker images in a PKGBUILD.

3) Rename this package to something like sentry9.1, freezing it at this version, and then pick options #1 or #2.

When I have some time this weekend, I may ask around for advice. There's no easy solution in this case, and I know from past experience with this package that there are some users who may be uninterested in running Sentry v10 if it requires configuring at least 3 other services. I will leave this package flagged for the time being in the hopes users of this package check here.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

zancarius commented on 2016-09-08 06:22

Updated to version 8.8.0. Thanks for the notification!

As always, report PKGBUILD bugs on my PKGBUILDs repository [1].

I now have mirrors configured elsewhere (see the README), so if you'd rather avoid GitHub or have a preference elsewhere, feel free to pick the host that suits your needs best and report bugs there.

[1] https://github.com/zancarius/archlinux-pkgbuilds

zancarius commented on 2016-06-10 05:24

Added.

libxml2 is probably also required as well, strictly speaking, it's just that pulling in libxslt also installs libxml2.

For completeness sake, I've updated the makedepends to include both. Apparently the notion of adding it to the split package depends array never fully percolated to the top when I was considering makedepends.

Good catch, thanks!

Ahti333 commented on 2016-06-10 04:40

The makedepends of the PKGBUILD should include libxslt as well. The python2-lxml egg won't build without it.

zancarius commented on 2016-06-06 17:49

Thanks Mitch!

I appreciate your feedback and help!

mitchhentges commented on 2016-06-06 17:44

It appears to be working, even after a reboot. No errors or anything. Thanks!

zancarius commented on 2016-06-06 17:42

I usually forget to fix things because I'm an idiot. ;)

Also, keep an eye out for the unit file changes. They've moved a ton of stuff and deprecated some of the old runners, so I've split things out. You should only have to run sentry.service now (systemctl start sentry), which is nice. Unfortunately, it also spawns a couple of other things (celery and celery-beat via "sentry run worker" and "sentry run cron"). I'd like to know if that works for you.

mitchhentges commented on 2016-06-06 17:40

Ah, I hadn't checked the upgrade instructions, because I'm a skrub.

zancarius commented on 2016-06-06 17:38

Did I forget to change that in the upgrade instructions? Looks like something I'd do.

mitchhentges commented on 2016-06-06 17:37

Ah, it's because, when upgrading sentry, I was running `/opt/sentry/bin/sentry --config /etc/sentry/sentry.conf.py upgrade", but it looks like now just the directory is specified for the --config option.

So: `/opt/sentry/bin/sentry --config /etc/sentry/ upgrade`

zancarius commented on 2016-06-06 17:35

Sentry's launcher has changed a bit as of 8.5.0. I might've missed something.