You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current version of ZendSentry for ZF2 is `2.3.1`. It supports Zend Framework >= 2.5.3. For older versions see the legacy branch and tags in the `1.*` series. For ZF3 compatible versions, please install releases in the `3.*` branch.
7
+
The current version of ZendSentry for ZF2 is `2.4.0`. It supports Zend Framework >= 2.5.3. For older versions see the legacy branch and tags in the `1.*` series. For ZF3 compatible versions, please install releases in the `3.*` branch.
8
8
9
-
#Latest Changes
10
-
- Possibility to add extra context to simple logs
11
-
- Add ZF3 compatible branch
12
-
- Switch Raven dependency to new official sentry/sentry repository
13
-
- Fix problem introduced by ZF BC break in ZF version 2.5.3 and branch of legacy branch
14
-
15
-
#Important Changes
16
-
- 3.0.1: ViewHelper fix for ZF3
17
-
- 3.0.0: Update to latest SDK dependencies and add ZF3 compatibility fixes
18
-
- 2.2.1: Update to `sentry/sentry` 1.5.0 and `ravenjs` 3.8.0, Fix: Only detach HttpExceptionStrategy if it exists
19
-
- 2.2.0: Update to `sentry/sentry` 0.21.2
9
+
# Important Changes
10
+
- 3.2.0 and 2.4.0: Upgrade dependencies to `sentry/sentry` 1.7.0 and `ravenjs` 3.17.0
11
+
- 3.0.1: ViewHelper fix
12
+
- 3.0.0: First ZF2 release with latest sentry SDK dependencies and ZF3 compatibility fixes
13
+
- 2.2.1: Fix: Only detach HttpExceptionStrategy if it exists
20
14
- 2.0.0: New major version for ZF >=2.5.3
21
15
- 1.5.2: Configurable error messages
22
16
- 1.4.0: Raven configuration can now be overwritten through ZendSentry configuration if needed
23
17
- 1.2.0: supports tags, every logging action returns the Sentry event_id, Raven is registered as Service
24
18
- 0.3.1: dedicated CLI ExceptionStrategy (credits to Mateusz Mirosławski)
25
19
26
-
#Introduction
20
+
#Introduction
27
21
28
-
##What's Sentry?
22
+
##What's Sentry?
29
23
[Sentry](https://www.getsentry.com/welcome/) is an online service to which you can log anything including your
30
24
exceptions and errors. Sentry creates nice reports in real time and aggregates your logged data for you.
31
25
32
-
##What's ZendSentry
26
+
##What's ZendSentry
33
27
It is a module that builds the bridge between your Zend Framework 2 application and the Sentry service. It's extremely
34
28
easy to setup and does a lot of things out-of-the-box.
35
29
@@ -44,14 +38,14 @@ Current features:
44
38
* Raven is registered as a Service
45
39
* override Raven config defaults
46
40
47
-
#Installation
41
+
#Installation
48
42
49
43
This module is available on [Packagist](https://packagist.org/packages/cloud-solutions/zend-sentry).
50
44
In your project's `composer.json` use:
51
45
52
46
{
53
47
"require": {
54
-
"cloud-solutions/zend-sentry": "2.3.1"
48
+
"cloud-solutions/zend-sentry": "2.4.0"
55
49
}
56
50
57
51
Run `php composer.phar update` to download it into your vendor folder and setup autoloading.
@@ -63,14 +57,14 @@ Add `ZendSentry` to the modules array in your `application.config.php`, preferab
63
57
64
58
That's it. There's nothing more you need to do, everything works at that stage, [try it](#try-it). Happy logging!
65
59
66
-
#Basic Automatic Usage
60
+
#Basic Automatic Usage
67
61
68
62
Again, you don't need to write a single line of code to make this work. The default settings will make sure Sentry
69
63
is registered as both error and exception handler, [try it](#try-it) by triggering and error or throwing around some
70
64
exceptions. You should instantly see them in your Sentry dashboard. ZendSentry also packages its own ExceptionStrategies
71
65
to make sure, exceptions ZF would otherwise intercept, are logged.
72
66
73
-
#Manual Usage
67
+
#Manual Usage
74
68
Additonally, the module registers a log event listener on application level. So you can trigger custom log events from
75
69
anywhere in your application.
76
70
@@ -107,7 +101,7 @@ exceptions manually by using the respective listener directly:
107
101
$eventID = $result->last();
108
102
}
109
103
110
-
#Using Tags
104
+
#Using Tags
111
105
112
106
You can also pass your own tags to Sentry. The service will automatically create filtering and sorting for these tags.
113
107
When using the `log` event, you can optionally pass tags like this:
@@ -131,7 +125,7 @@ If using the `logException` event manually, you can also pass along tags:
131
125
132
126
See how to use tags for automagically logged exceptions below.
133
127
134
-
#Raven as Service
128
+
#Raven as Service
135
129
136
130
The module registers the Raven_Client as an application wide service. Usually you don't want to access it directly
137
131
because triggering the event listeners leaves you with cleaner code. One example where the direct usage of Raven can
@@ -156,7 +150,7 @@ You might want to do something like this e.g. in your `AbstractActionController:
156
150
);
157
151
}
158
152
159
-
#Configuration options
153
+
#Configuration options
160
154
161
155
Just for the record, a copy of the actual global configuration options:
162
156
@@ -227,7 +221,7 @@ Just for the record, a copy of the actual global configuration options:
227
221
*/
228
222
'raven-config' => array(),
229
223
230
-
#Try it
224
+
#Try it
231
225
A few ideas how to try the different features from a Controller or View:
0 commit comments