UNPKG

@kvaser/canking-api

Version:

CanKing API to communicate with the CanKing service using Node.js.

83 lines (46 loc) • 2.25 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
[**Kvaser CanKing GUI Extensions SDK v7.5.1**](../../README.md) *** [Kvaser CanKing GUI Extensions SDK](../../modules.md) / [models](../README.md) / LogLevel # Enumeration: LogLevel Possible log levels. NOTE (known proto3 deviation): The zero value is LOG_LEVEL_TRACE rather than LOG_LEVEL_UNSPECIFIED. This is intentional because the backend maps these values directly to the host logging framework's integer levels (0 = Trace). Changing the zero value would require cascading changes across the service implementation. Consumers should not rely on default-constructed messages having a neutral log level. ## Enumeration Members ### LOG\_LEVEL\_CRITICAL > **LOG\_LEVEL\_CRITICAL**: `5` LOG_LEVEL_CRITICAL - Logs that describe an unrecoverable application or system crash, or a catastrophic failure that requires immediate attention. *** ### LOG\_LEVEL\_DEBUG > **LOG\_LEVEL\_DEBUG**: `1` LOG_LEVEL_DEBUG - Logs that are used for interactive investigation during development. These logs should primarily contain information useful for debugging and have no long-term value. *** ### LOG\_LEVEL\_ERROR > **LOG\_LEVEL\_ERROR**: `4` LOG_LEVEL_ERROR - Logs that highlight when the current flow of execution is stopped due to a failure. These should indicate a failure in the current activity, not an application-wide failure. *** ### LOG\_LEVEL\_INFORMATION > **LOG\_LEVEL\_INFORMATION**: `2` LOG_LEVEL_INFORMATION - Logs that track the general flow of the application. These logs should have long-term value. *** ### LOG\_LEVEL\_NONE > **LOG\_LEVEL\_NONE**: `6` LOG_LEVEL_NONE - Not used for writing log messages. Specifies that a logging category should not write any messages. *** ### LOG\_LEVEL\_TRACE > **LOG\_LEVEL\_TRACE**: `0` LOG_LEVEL_TRACE - Logs that contain the most detailed messages. These messages may contain sensitive application data. These messages are disabled by default and should never be enabled in a production environment. *** ### LOG\_LEVEL\_WARNING > **LOG\_LEVEL\_WARNING**: `3` LOG_LEVEL_WARNING - Logs that highlight an abnormal or unexpected event in the application flow, but do not otherwise cause the application execution to stop. *** ### UNRECOGNIZED > **UNRECOGNIZED**: `-1`