2
0

222 Commits

Author SHA1 Message Date
630bba4026 bumb minor version 2020-07-19 02:13:00 +02:00
201c44ac92 remove exotic compose args 2020-07-19 02:11:15 +02:00
e712e5d9c0 bumb yandex image 2020-07-19 02:04:51 +02:00
aa2b037a31 fuck alpine images 2020-07-19 01:57:11 +02:00
cc00f13133 proper portbind 2020-07-19 01:55:45 +02:00
a6ca0a9033 remove github stuff 2020-07-19 01:49:00 +02:00
4dbfcbcebe ci(release): Fix quotes for auto version setting 2020-07-18 01:26:47 +03:00
17d97e13c0 ci(release): Smarter and safer auto version setting
If the release action is run without an explicit version in the same calendar month more than once, all of them will try to release the same version where the patch version is set to 0. This is never the intended action: if we are making a new release in the same month where an old one exists, it is 100% a patch release.

This PR automatically implements patch version increment based on existing versions.
2020-07-17 22:34:11 +03:00
094d8e38a3 fix(install): Read and set .env in install.sh (#600)
Fixes #597.
2020-07-17 15:29:55 +03:00
86864d0edf feat(compose): Add ability to use custom images for any Sentry service (#602)
This change allows one to override any Sentry service image, mostly for testing purposes. It also removes the SENTRY_VERSION variable as docker-compose makes it very hard to cascade default values for these. Next step is to have integration tests in getsentry/snuba and getsentry/relay (and possibly for getsentry/symbolicator) for getsentry/onpremise using this PR.

Also related: #596.
2020-07-17 15:02:45 +03:00
e82506f5b7 fix(snuba): Add consumer group to transactions consumer (#599)
Without the consumer-group option, transactions consumer and events consumer will compete for messages on the same topic and usually events win, which is the first one. This may cause some data loss for performance and make it seem not work.

Should address https://forum.sentry.io/t/perfomance-tracing-for-sentry-itself/10405/5?u=byk
2020-07-17 06:50:36 +03:00
0bf688a0a6 ci: Increase timeout for getting test event
Travis CI failed waiting on this multiple times so increase the grace period. Turns out during peak times things get slow.
2020-07-15 22:53:56 +03:00
b0577a3b27 ci(craft): Add delay between prepare and publish 2020-07-15 22:42:46 +03:00
9330b36415 ci(craft): Fix Travis CI check name after .com migration 2020-07-15 21:06:15 +03:00
cb83593d5b feat(snuba): Add transactions consumer (#595)
Needed for Performance to work (see #586).

Depends on #593. Fixes #588.
2020-07-15 21:00:37 +03:00
4f39b57a53 install(clickhouse): Ensure we have the newest transactions table (#594)
See getsentry/sentry#19882 and getsentry/sentry/#19883.

Fixes #587.
2020-07-15 20:37:51 +03:00
0a9f12404a fix(license): License change date should be 3 years later, not now
Follow up to #584.
2020-07-14 22:19:47 +03:00
1a554ba61b meta(release): Update BSL date on release (#584) 2020-07-14 22:12:30 +03:00
911f17f080 feat: Enable performance views for on-premise (#586)
The discover-basic and discover-query feature flags are enabled by
default in the built-in sentry/conf/server.py

Closes #582
2020-07-14 21:48:22 +03:00
bb2b37a065 test: Improve cosmetics, remove docker-compose logs 2020-07-14 01:44:07 +03:00
0ef9bf5721 test(gcb): Even more debug info on fail 2020-07-14 01:29:44 +03:00
f922986403 test(gcb): Add more debug info for GCB fails 2020-07-14 01:09:02 +03:00
35e817ceb4 fix(gcb): Don't use uuidgen as it doesn't exist on GCB 2020-07-14 00:48:35 +03:00
61ec4166d1 fix(test): Don't use sentry-cli for test event (#585)
Running Docker on the host network is not supported on GCB, which is breaking our builds over at getsentry/sentry. This patch removes the use of sentry-cli and does a manual `curl` request to create the test event.
2020-07-14 00:31:46 +03:00
a2507c10e0 fix(superuser): Don't set INTERNAL_IPS to Docker network (#581)
`INTERNAL_IPS` is used to check whether to allow superuser access or not. Limiting this to the Docker internal network makes it impossible for anyone to reach admin pages with on-premise setup.

This is a follow up to #572 and it fixes #577.
2020-07-13 19:21:52 +03:00
75fe6c073b fix(ingest): Fix Relay auth issues and add e2e event ingestion test (#578)
This is a long-needed test that tests the whole pipeline from Nginx, Relay, to Kafka, and Snuba. The final missing piece is testing the Symbolicator integration.

This PR is also a follow up to #576 as it didn't solve the Relay issues fully (the earlier fix was a coincidence or is not as reliable as it seemed).

Fixes #486 (finally?).
2020-07-13 13:07:05 +03:00
1c9bfd9017 fix(relay): Fix relay cannot authenticate w/ Sentry (#576)
Fixes #486.

I finally figured out what the issue was: a missing `post-buffering` option to let Relay finish it's POST request for auth. This PR supersedes #543.
2020-07-11 00:08:14 +03:00
73213bc51f ref(relay): Remove PK and rely on INTERNAL_IPS (#572)
This patch adds `INTERNAL_IPS` definition to `sentry.conf.py` by sniffing the network from eth0 and relies on this for trusted Relays instead of the ALLOWLISTED PKs. This removes the necessity of syncing Relay PKs to `sentry.conf.py`.

This PR needs getsentry/sentry#19798 to work.
2020-07-10 23:53:50 +03:00
9d44b99c55 fix(slack): Point to newer docs, better defaults (#571)
* added new default going forward uncommented
* added link to new guide
* added support for new signing-secret
* slight rejig to config
2020-07-10 21:10:05 +03:00
96889a6175 Add volumed-out config directory for symbolicator. (#566)
I would like to be able to customize the configuration for my Sentry 10 symbolicator instance, which this change allows me to easily do.

See related: https://github.com/getsentry/symbolicator/issues/245

Co-authored-by: Burak Yigit Kaya <ben@byk.im>
2020-07-08 20:42:33 +03:00
a01d013617 fix(slack): Add note about legacy app flag for newly created bots (#563)
Co-authored-by: jack <jackc@strangeanimals.com.au>
2020-07-08 15:56:49 +03:00
a549ab1300 license: Update BSL change date (#557)
Co-authored-by: sentry-update-license-date[bot] <57668832+sentry-update-license-date[bot]@users.noreply.github.com>
2020-07-03 22:06:19 +03:00
e75e6f1dee fix(zookeeper): cp: cannot create regular file (#552)
Hi,

I've been through quite a few different ways of implementing this fix and settled on creating a variable to store the output of checking whether the zookeeper copy target folder exists and copying the snapshot file based on the copy target folder existing. I've ran quite a few manual tests for each option as well. Currently the PR sits on Option 3 from the below options.

**Option 1**
Judging from the [Jira issue](https://issues.apache.org/jira/browse/ZOOKEEPER-3056), it seems like the work around for zookeeper upgrades could be omitted entirely since the issue relates to upgrades from v3.4.10 to v3.5.4. I've tested removing the zookeeper workaround entirely and that install ran smoothly on a clean install of Sentry (no existing data) as well as an install of Sentry that currently has very minimal amount of log entries (roughly 100 log entries). Could we possibly remove the workaround entirely? 

**Option 2**
The second option was to simply add a check to the currently [existing line](https://github.com/getsentry/onpremise/blob/master/install.sh#L178) of whether the copy target folder exists and perform the snapshot file copy only if the copy target folder exists. This is the least amount of code and possibly the simpler fix while also setting the `ZOOKEEPER_SNAPSHOT_TRUST_EMPTY` env var to `true`, however, some unnecessary calculations will be done to determine the `ZOOKEEPER_LOG_FILE_COUNT` and `ZOOKEEPER_SNAPSHOT_FILE_COUNT`.

**Option 3**
I've created a variable to store whether the copy target folder exists and proceed with the zookeeper upgrade workaround only if the copy target folder exists. This means that if the copy target folder does not exist, the env var `ZOOKEEPER_SNAPSHOT_TRUST_EMPTY` will not be set.

Fixes #547.

Co-authored-by: chamirb <chamirb@globalkinetic.com>
2020-06-29 16:16:42 +03:00
131a324af2 docs: Rename title from 10 to Nightly 2020-06-17 20:56:24 +03:00
f66ca96fa7 build(gha): Add skip_prepare option for manual triggers 2020-06-16 23:11:09 +03:00
ea93a4b886 build(gha): Add GH status context 2020-06-16 22:58:52 +03:00
b2b497e619 build(gha): Workaround for Craft action params 2020-06-16 22:55:03 +03:00
d83aa55bf8 build(gha): Add name to release action 2020-06-16 22:49:00 +03:00
ea2c31f012 build(gha): Add GIT_*_NAME variables 2020-06-16 22:48:09 +03:00
2fc9811c74 build(gha): Add automated CalVer releases (#539) 2020-06-16 12:44:13 +03:00
cfaa368306 fix(gha): Add version to craft-action 2020-06-14 17:36:53 +03:00
8c7b633b90 fix(gha): Fix indent in yaml file 2020-06-14 17:29:34 +03:00
af502d0ba5 build(gha): Add Craft releases as a GitHub action (#538) 2020-06-14 17:27:41 +03:00
677e753c18 fix(relay): Increase Kafka message size limit to 50MB (#527)
Based on my forum post https://forum.sentry.io/t/sentry-native-and-kafka-messagesizetoolarge-error/9948
In short I tried to send minidumps more than 1mb(in fact 2mb), and relay service failed to store event, with kafka error `MessageSizeTooLarge`.
You can reproduce this if you recreate install this on local machine, create simple native project, and send minidump file more than 1mb via curl like suggested in docs or in web ui. And check the logs.

I reason selected value of 50mb on https://github.com/getsentry/onpremise/blob/master/docker-compose.yml#L87, like you already hardcoded on kafka service.
2020-06-11 22:33:36 +03:00
c2120aafc9 fix(zookeeper): Temp ZK fix should run in detached mode (#525)
Fixes #519.
2020-06-02 19:45:07 +03:00
ff057d1d2c feat: Add sessions snuba consumer to setup (#524)
Co-authored-by: Markus Unterwaditzer <markus@unterwaditzer.net>
Co-authored-by: Burak Yigit Kaya <byk@sentry.io>
2020-06-02 17:04:46 +03:00
3522a12325 ref(sentry): Remove explicit Discover v2 flags (#523)
Discover v2 is now enabled by default: getsentry/sentry#19023
2020-06-01 23:34:54 +03:00
41f8b0f149 license: Update BSL change date (#522)
Co-authored-by: sentry-update-license-date[bot] <57668832+sentry-update-license-date[bot]@users.noreply.github.com>
2020-06-01 18:05:19 +03:00
01bec99996 fix(nginx): Increase upload size back to 100M for Sentry too
Addresses https://github.com/getsentry/onpremise/pull/499#discussion_r431537129
2020-05-28 21:42:58 +03:00
85f267bec7 fix(nginx): Increase upload size back to 100M for store
Addresses https://github.com/getsentry/onpremise/pull/499#discussion_r431537129
2020-05-28 21:33:57 +03:00