Details
-
Type:
New Feature
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:4
-
Sprint:Sprint 32
Description
We have a nice opportunity to take advantage of OSGi remote services to remotely log (http://wiki.osgi.org/wiki/Remote_Service_Admin) errors occurring in the wild. The IGB application would be the consumer of our remote logging error service and would append error logs in an asynchronous way to avoid any impact on application performance.
This new service could potentially radically change our ability to learn about and patch bugs. If integrated into our existing ELK stack infrastructure, we could get "real time" visibility into the errors occurring int he application.
We could also use these logs to notify APP developers when errors are occurring in their apps.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Description |
We have a nice opportunity to take advantage of OSGi remote services to remotely log errors occurring in the wild. The IGB application would be the consumer of our remote logging error service and would append error logs in an asynchronous way to avoid any impact on application performance.
This new service could potentially radically change our ability to learn about and patch bugs. If integrated into our existing ELK stack infrastructure, we could get "real time" visibility into the errors occurring int he application. |
We have a nice opportunity to take advantage of OSGi remote services to remotely log errors occurring in the wild. The IGB application would be the consumer of our remote logging error service and would append error logs in an asynchronous way to avoid any impact on application performance.
This new service could potentially radically change our ability to learn about and patch bugs. If integrated into our existing ELK stack infrastructure, we could get "real time" visibility into the errors occurring int he application. We could also use these logs to notify APP developers when errors are occurring in their apps. |
| Description |
We have a nice opportunity to take advantage of OSGi remote services to remotely log errors occurring in the wild. The IGB application would be the consumer of our remote logging error service and would append error logs in an asynchronous way to avoid any impact on application performance.
This new service could potentially radically change our ability to learn about and patch bugs. If integrated into our existing ELK stack infrastructure, we could get "real time" visibility into the errors occurring int he application. We could also use these logs to notify APP developers when errors are occurring in their apps. |
We have a nice opportunity to take advantage of OSGi remote services to remotely log (http://wiki.osgi.org/wiki/Remote_Service_Admin) errors occurring in the wild. The IGB application would be the consumer of our remote logging error service and would append error logs in an asynchronous way to avoid any impact on application performance.
This new service could potentially radically change our ability to learn about and patch bugs. If integrated into our existing ELK stack infrastructure, we could get "real time" visibility into the errors occurring int he application. We could also use these logs to notify APP developers when errors are occurring in their apps. |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs Testing [ 10002 ] |
| Sprint | Sprint 31 [ 39 ] |
| Sprint | Sprint 32 [ 40 ] |
| Rank | Ranked higher |
| Rank | Ranked lower |
| Status | Needs Testing [ 10002 ] | Testing In Progress [ 10003 ] |
| Assignee | David Norris [ dcnorris ] | Mason Meyer [ mason ] |
| Resolution | Done [ 10000 ] | |
| Status | Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Workflow | Loraine Lab Workflow [ 16941 ] | Fall 2019 Workflow Update [ 19751 ] |
| Workflow | Fall 2019 Workflow Update [ 19751 ] | Revised Fall 2019 Workflow Update [ 21870 ] |