forked from collective/collective.sentry
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.txt
54 lines (35 loc) · 1.18 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
collective.sentry
=================
Sentry integration with Zope.
Requirements
------------
* Plone 5.2 (tested)
* Python 3.6+ (tested)
Installation
------------
Add `collective.sentry` to your buildout and re-run buildout.
Configuration
-------------
Configure the Sentry DSN by setting the environment variable `SENTRY_DSN` inside your shell configuration or using buildout::
[instance]
environment-vars +=
SENTRY_DSN https://......
Supplementary information logged in Sentry
------------------------------------------
`collective.sentry` will create automatically a Sentry tag `instance_name`
which is derived from the buildout part name of the related instance. An
additional tag `project` can be configured (optional) if you set the
environment variable `DSN_PROJECT`. This allows you introduce an additional
tag for filtering, if needed.
Repository
----------
https://github.com/collective/collective.sentry
Licence
-------
- GPL2 - GNU Public License 2
- based on `raven.contrib.zope`: BSD
Author
------
ZOPYX/Andreas Jung, info@zopyx.com
`collective.sentry` has been developed as part of a Plone 5.2 migration project and it
sponsored by the University Gent.