-
```
Rather than logging to a centralized database, ELMAH could send a
JSON-serialized exception to a user-specified endpoint to allow centralized
exception logging. This would remove the need for a …
-
```
Rather than logging to a centralized database, ELMAH could send a
JSON-serialized exception to a user-specified endpoint to allow centralized
exception logging. This would remove the need for a …
-
## Product Outline
[Link](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/product-outline-template.md)
## High Level User Story/ies
As a _____, I…
-
```
Rather than logging to a centralized database, ELMAH could send a
JSON-serialized exception to a user-specified endpoint to allow centralized
exception logging. This would remove the need for a …
-
```
Rather than logging to a centralized database, ELMAH could send a
JSON-serialized exception to a user-specified endpoint to allow centralized
exception logging. This would remove the need for a …
-
Request data display page should:
- fetch request JSON either from the logger's own data resource and/or from the metadb web service (assuming that the request had made it INTO the metadb database to …
ao508 updated
2 years ago
-
This is meant to lessen the development burden to support Elastic Logging natively by the application or any direct centralized logging solution
Take into consideration the below:
- Logs are wri…
-
Logging in the client side should be centralized with a logging library.
Some more information.
-
```
Rather than logging to a centralized database, ELMAH could send a
JSON-serialized exception to a user-specified endpoint to allow centralized
exception logging. This would remove the need for a …
-
```
Rather than logging to a centralized database, ELMAH could send a
JSON-serialized exception to a user-specified endpoint to allow centralized
exception logging. This would remove the need for a …