Support aggregation
No due date
0% complete
- An example of aggregation: say your app receives status updates and picture posts, some event names could be:
-
-
<li>jms.messages.received.statusupdate.ok = 155</li> -
<li>jms.messages.received.statusupdate.failed = 1</li> -
<li>jms.messages.received.statusupdate.malformed = 6</li> -
<li>jms.messages.received.picturepost.ok = 77</li> -
<li>jms.messa…
-
- An example of aggregation: say your app receives status updates and picture posts, some event names could be:
-
-
<li>jms.messages.received.statusupdate.ok = 155</li> -
<li>jms.messages.received.statusupdate.failed = 1</li> -
<li>jms.messages.received.statusupdate.malformed = 6</li> -
<li>jms.messages.received.picturepost.ok = 77</li> -
<li>jms.messages.received.picturepost.toobig = 9</li>
-
- If logical, the library could automatically calculate aggregate values if it makes sense. This could look like:
-
-
<li>jms.messages.received.statusupdate.ok = 155</li> -
<li>jms.messages.received.statusupdate.failed = 1</li> -
<li>jms.messages.received.statusupdate.malformed = 6</li> -
<li>jms.messages.received.statusupdate = 162</li> -
<li>jms.messages.received.picturepost.ok = 77</li> -
<li>jms.messages.received.picturepost.toobig = 9</li> -
<li>jms.messages.received.picturepost = 86</li> -
<li>jms.messages.received = 248</li>
-