Changes
Serilog is a portable and structured logging framework to record diagnostic logs into files, console and SQL/NoSQL databases.
<!-- DO NOT REMOVE THIS -->{{Template:Activity/Begin}}<!-- DO NOT REMOVE THIS -->
= Description =
{{ActivityInfoBox
| title = Serilog
| name = Serilog
| image =
| imagecaption =
| purpose = Structured logging framework to record diagnostic logs into files, console and SQL/NoSQL databases.
| category = UBIK
| returns = true if successful
| version = 3.5.0+
}}
===Arguments===
{| class="wikitable sortable" | width = "50%"
|-
! Argument !! Purpose
|- align="left"
| Verbose || is the noisiest level, generally used only as a last resort when debugging a difficult problem, and rarely (if ever) enabled for a production app. For example, local variables within an algorithm implementation might be logged at this level.
|- align="left"
| Debug | || Debug is used for internal system events that are not necessarily observable from the outside, but useful when determining how something happened. For example, the details of requests and responses made to and from external integration points would often be logged at this level.
|- align="left"
| Information || Information events describe things happening in the system that correspond to its responsibilities and functions. Generally, these are the observable actions the system can perform. For example, processing a payment or updating a user's details will be logged at this level.
|- align="left"
| Warning || When service is degraded, endangered, or may be behaving outside of its expected parameters, Warning level events are used. A warning event should only be emitted when the condition is either transient or can be investigated and fixed - use restraint to avoid polluting the log with spurious warnings. For example, slow response times from a critical database would be logged as warnings.
|- align="left"
| Error || When functionality is unavailable or expectations broken, an Error event is used. For example, receiving an exception when trying to commit a database transaction is an event at this level.
|- align="left"
| Fatal || The most critical level, Fatal events demand immediate attention. For example, an application failing during startup will log a Fatal event. If you have a pager, it goes off when one of these occurs.
|- align="left"
|}
===Usage===
Usa
=Example=
Exemplary values to get Customizing Info from UBIK Content service.
{| class="wikitable" | width = "25%"
|-
! RESTGet!! Value
|- align="left"
| DisplayName || RESTGet<String
|- align="left"
| Error ||
|- align="left"
| Headers ||
|- align="left"
| MethodName || "GetCustomizingInfo"
|- align="left"
| Parameter ||
|- align="left"
| Resonse ||
|- align="left"
| Result || "info"
|- align="left"
| Url || "https://81.10.184.186:888/UBIK/DBG/AUG/MT/TEMPLATE/Content/UbikContent.svc"
|}
{| class="wikitable" | width = "50%"
|-
! DebugMessage!! Value
|- align="left"
| DisplayName || DebugMessage
|- align="left"
| Result ||
|- align="left"
| Text || "info"
|- align="left"
| UBIKObject ||
|- align="left"
|}
<!-- DO NOT REMOVE THIS -->{{Template:Activity/End}}<!-- DO NOT REMOVE THIS -->
==See also==
* [[Configure Logging]]
==Useful links [What is Serilog and Tutorial]==
* https://serilog.net/
