Commit Graph

1320 Commits

Author SHA1 Message Date
Klaas van Schelven
d3de2e6d5b Add '--window' param to showstat 2025-04-17 12:20:11 +02:00
Klaas van Schelven
21dfa6dbbc Show stat command: add column for 'write saturation 2025-04-17 12:18:09 +02:00
Klaas van Schelven
2a871b06d4 conf_templates: STATS_RETENTION_MINUTES configurable 2025-04-17 11:00:43 +02:00
Klaas van Schelven
731d446a3d snappea task warning should itself never slow down the site
(max at 0.1s)
2025-04-17 11:00:43 +02:00
Klaas van Schelven
5379f9a168 Simple page for object counts (superuser) 2025-04-17 11:00:42 +02:00
Klaas van Schelven
7616b0ea77 Document timing of task.create/delete in code 2025-04-17 10:16:43 +02:00
Klaas van Schelven
89927c7ab4 Snappea stats: never bring down snappea 2025-04-17 10:13:19 +02:00
Klaas van Schelven
6500548168 Snappea Stats: document the need for separate table 2025-04-17 09:41:03 +02:00
Klaas van Schelven
abd05b7269 Snappea stats: silently ignore backwards clock drift 2025-04-17 09:38:42 +02:00
Klaas van Schelven
b3c99fda72 Add 'munin' command
(initial target market: me)
2025-04-17 09:01:42 +02:00
Klaas van Schelven
fb45a8ccc9 Show stats command for snappea 2025-04-16 21:48:41 +02:00
Klaas van Schelven
4cedffc1b7 Snappea stats: configurable retention 2025-04-16 17:10:15 +02:00
Klaas van Schelven
06342010dd Turn off KEEP_ENVELOPES in development
as per the documented caveats, I'd rather not do this when not
necessary (when not actively looking for malformed envelopes)
2025-04-16 16:59:15 +02:00
Klaas van Schelven
e27439ab7b snappea stats: log cost of stats themselves 2025-04-16 16:57:53 +02:00
Klaas van Schelven
94338051ef Snappea Stats: first version 2025-04-16 16:40:28 +02:00
Klaas van Schelven
67f769d3e5 immediate_semaphore: implement using
Given what immediate_semaphore _is_, the principled need for this is obvious.
In practice, this wasn't needed yet (immediate_atomic is not used for
any non-default DB). But better fix it before we do decide on that.
2025-04-16 13:55:22 +02:00
Klaas van Schelven
f8db5edf82 immediate atomic 'get-write-lock' performance logging: fix it
it was reporting the actual sqlite get-write-lock timings, but since the
introduction of the immediate_semaphore those were 'basically never' blocking
since all the blocking was done in the semaphore (ignoring cross
gunicorn/snappea details)
2025-04-16 12:53:42 +02:00
Klaas van Schelven
8c87d0fe13 When is the email_system_warning shown? change & document
as per the comment
2025-04-16 09:55:41 +02:00
Klaas van Schelven
3f429c2773 Clarify options for EMAIL_BACKEND in the conf_templates 2025-04-16 09:36:34 +02:00
Klaas van Schelven
a74913e6ea Warning about the specialness of the snappea DB 2025-04-15 10:06:36 +02:00
Klaas van Schelven
6ff303858b Oldest task age warning: display as int 2025-04-15 10:02:54 +02:00
Klaas van Schelven
2cc103c954 Merge pull request #81 from bugsink/dependabot/pip/python-packages-7c96208a08
Update sentry-sdk requirement from ==2.25.* to ==2.26.* in the python-packages group
2025-04-15 09:31:43 +02:00
Klaas van Schelven
748062a311 EVENT_STORAGES: add (commented-out) example configuration to conf_templates 2025-04-14 21:32:38 +02:00
dependabot[bot]
c235e79370 Update sentry-sdk requirement in the python-packages group
Updates the requirements on [sentry-sdk](https://github.com/getsentry/sentry-python) to permit the latest version.

Updates `sentry-sdk` to 2.26.0
- [Release notes](https://github.com/getsentry/sentry-python/releases)
- [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md)
- [Commits](https://github.com/getsentry/sentry-python/compare/2.25.0...2.26.0)

---
updated-dependencies:
- dependency-name: sentry-sdk
  dependency-version: 2.26.0
  dependency-type: direct:production
  dependency-group: python-packages
...

Signed-off-by: dependabot[bot] <support@github.com>
2025-04-14 15:50:10 +00:00
Klaas van Schelven
dd339f73de One more fix for psycopg<3.0.17
see ce9d0e4941
2025-04-14 11:49:41 +02:00
Klaas van Schelven
1908fede13 CHANGELOG for 1.5.0 2025-04-14 11:48:00 +02:00
Klaas van Schelven
ce9d0e4941 Fix for psycopg<3.0.17 2025-04-14 11:29:12 +02:00
Klaas van Schelven
712eb63faa Merge pull request #80 from bugsink/sourcemaps-spike
Sourcemaps: first version
2025-04-14 11:08:19 +02:00
Klaas van Schelven
53db317529 Refactoring (rename): UserModel -> User
which I'd say is the idiomatic way
2025-04-14 10:43:08 +02:00
Klaas van Schelven
6bcbaa71b9 Support 'sentry-cli login'
like so:

```
$ sentry-cli --url http://bugsink:8000/ login
This helps you signing in your sentry-cli with an authentication token.
If you do not yet have a token ready we can bring up a browser for you
to create a token now.

Sentry server: bugsink
Open browser now? [y/n] y
```

See https://github.com/getsentry/sentry/issues/82078
2025-04-14 10:40:54 +02:00
Klaas van Schelven
f56e3c647a Auth Tokens: a UI 2025-04-14 10:35:37 +02:00
Klaas van Schelven
4bbfe1a4ff Files: use the appropriate db transactions 2025-04-14 09:55:15 +02:00
Klaas van Schelven
70b8afb842 Factor out assemble_artifact_bundle into an async task
I did not do any research into actual timings (i.e. whether there really is a
need to pull this out of the request/response loop) but it seems somewhat
prudent.  Because Sentry also does this (and does it at this point), the whole
thing of matching Sentry's interface is not being complicated by it (if
anything: the contrary).
2025-04-14 09:37:05 +02:00
Klaas van Schelven
921d5bd4a3 Add EMAIL_USE_SSL to settings/conf_templates
This is the settings for implicit SSL/TLS on port 465 (rather than STARTTLS on port 587)
2025-04-12 21:36:52 +02:00
Klaas van Schelven
50343c0b2c Document further thoughts on store-envelopes in DB 2025-04-12 21:28:04 +02:00
Klaas van Schelven
f95927ffd6 annotate_with_meta: add a case for (typically Filtered) string 2025-04-11 22:40:51 +02:00
Klaas van Schelven
47e2824d9a For CSRF_REASON mismatch message: point at settings also 2025-04-11 21:43:10 +02:00
Klaas van Schelven
485df1aed9 AuthToken: ability to create using a command 2025-04-11 14:45:37 +02:00
Klaas van Schelven
294105170b Remove debugging-line 2025-04-11 14:31:02 +02:00
Klaas van Schelven
895da36adc AuthToken: barebones implementation 2025-04-11 14:30:29 +02:00
Klaas van Schelven
1084796763 When not dogfooding, just print a regular stacktrace in the logs
This will hopefully help when getting issue-reports for those that
have not set up dogfooding.

See [Dogfooding Bugsink](https://www.bugsink.com/docs/dogfooding/)
2025-04-11 13:22:37 +02:00
Klaas van Schelven
ce3f2d9e8e Add files to .coveragerc 2025-04-11 11:24:50 +02:00
Klaas van Schelven
0c11bf0787 Add trivial viewtest 2025-04-11 11:19:03 +02:00
Klaas van Schelven
5d01214752 Sourcemaps: a test
See #19
2025-04-11 10:32:13 +02:00
Klaas van Schelven
b160a6df06 Files: downloadable from admin
for convenience
2025-04-11 09:15:09 +02:00
Klaas van Schelven
594144f04d Add chunked (transfer) encoding to send_json command
Back when fixing #9, a test-command wasn't added.

See #8, See #9
2025-04-10 21:17:15 +02:00
Klaas van Schelven
0bd899fdfa File.filename (for display purposes) 2025-04-10 17:00:46 +02:00
Klaas van Schelven
87130043e3 PoC of using sourcemaps in the UI
See #19
2025-04-10 15:52:34 +02:00
Klaas van Schelven
eb266d805c PoC of uploading sourcemap artifact bundles
* debug_id-only
* various TODOs (e.g. auth, async, retention)

See #19
2025-04-10 10:30:30 +02:00
Klaas van Schelven
d572ff3601 Fix warning on CSRF view
When the CSRF view is rendered, no RequestContext is used. This means the token
used for the logout link on the regular base.html won't work.

> UserWarning: A {% csrf_token %} was used in a template, but the context did not
> provide the value.  This is usually caused by not using RequestContext.
2025-04-09 14:12:39 +02:00