Enable logging for functions
Set the logging level for an instance of a StackState function

Overview

For debugging purposes, it may be helpful to enable logging for a StackState function. You can add logging statements to functions and then use the StackState CLI to set the logging level for individual instances of a check function, event handler function, propagation function or view state configuration function. Log messages will be added to the StackState log file stackstate.log. It is not currently possible to enable logging for other function types.

Set the logging level for a function instance

To enable logging for an instance of a function, use its ID to set a logging level in the StackState CLI. Note that the function itself will have an ID and each instance of the function relating to a component or view in StackState will have a separate ID.
The logging level should be set using the ID for an instance of a function, not the ID of the function itself.
  1. 1.
    Find the ID for the instance of the function that you want to enable logging for:
  2. 2.
    Use the StackState CLI to set the logging level for the ID, for example:
    1
    sts serverlog setlevel <id> DEBUG
    Copied!
  3. 3.
    Monitor the stackstate.log using the function instance ID.
    1
    tail -f stackstate.log | grep <id>
    Copied!

Add logging statements to a function

Logging statements can be added to StackState functions and monitored in the stackstate.log file. This is useful for debug purposes.
  1. 1.
    Add a log statement in the function's code. For example:
    • log.info("message")
    • log.info(variable.toString())
  2. 2.
    ​Set a logging level to enable logging for an instance of the function.

Find the ID for a function instance

Retrieve the ID for a specific instance of a function:

StackState CLI

Event handler IDs

The ID for an event handler can be found using the StackState CLI. This is the ID for an instance of an event handler function.
  • To list all event handlers, run the StackState CLI command below.
  • Use the id from the command output to enable logging for a specific event handler.
CLI command
Example result
1
sts graph list EventHandler
Copied!
1
id type name description owned by manual last updated
2
--------------- ------------ ------------ ------------- ---------- -------- ------------------------
3
114118706410878 EventHandler demo_handler True Fri Nov 13 11:32:29 2020
Copied!

View health state configuration IDs

The ID for a view health state configuration can be found using the StackState CLI. This is the ID for a view's instance of a view health state configuration function.
  • Run the two StackState CLI commands below:
    1. 1.
      To return the IDs of all StackState views.
    2. 2.
      To retrieve the JSON for a specific view ID.
  • Use the viewHealthStateConfiguration ID from the retrieved view JSON to enable logging for this instance of the view health state configuration function. In the example below, this would be 39710412772194.
CLI command
Example result
1
# get IDs of all views
2
sts graph list QueryView
3
​
4
# get the ID of the specified view's "viewHealthStateConfiguration"
5
sts graph show-node <VIEW_ID>
Copied!
1
$ sts graph list QueryView
2
id type name description owned by manual last updated
3
--------------- --------- ------------------------- ------------- ---------------------------- -------- ------------------------
4
9161801377514 QueryView Demo - Customer A - urn:stackpack:demo-stackpack False Fri Nov 13 16:24:38 2020
5
199988472830315 QueryView Demo - Customer B - urn:stackpack:demo-stackpack False Fri Nov 13 16:24:38 2020
6
278537340600843 QueryView Demo - Business Dashboard - urn:stackpack:demo-stackpack False Fri Nov 13 16:24:38 2020
7
​
8
​
9
$ sts graph show-node 9161801377514
10
​
11
{
12
"id":9161801377514,
13
"lastUpdateTimestamp":1605284678082,
14
"name":"Demo - Customer A",
15
"groupedByDomains":true,
16
"groupedByLayers":true,
17
"groupedByRelations":true,
18
"showIndirectRelations":true,
19
"showCause":"NONE",
20
"state":{
21
"id":212230744931364,
22
"lastUpdateTimestamp":1605284689666,
23
"state":"CLEAR",
24
"_type":"ViewHealthState"
25
},
26
"viewHealthStateConfiguration":{
27
"id":39710412772194,
28
"lastUpdateTimestamp":1605284678082,
29
"function":28286436254116,
30
"enabled":true,
31
"arguments":[
32
{
33
"id":128484527572993,
34
"lastUpdateTimestamp":1605284678082,
35
"parameter":184761614904259,
36
"value":1,
37
"_type":"ArgumentLongVal"
38
},
39
{
40
"id":229304367255010,
41
"lastUpdateTimestamp":1605284678082,
42
"parameter":178411912509267,
43
"value":1,
44
"_type":"ArgumentLongVal"
45
}
46
],
47
"_type":"ViewHealthStateConfiguration"
48
},
49
"groupingEnabled":true,
50
"minimumGroupSize":4,
51
"query":"(domain IN (\"customer E\") AND layer IN (\"API\", \"applications\", \"business application\", \"hypervisor\", \"databases\", \"k8s_proc\", \"lambda\", \"network devices\", \"location\", \"rack\", \"row\", \"servers\", \"services\", \"storage\"))",
52
"queryVersion":"0.0.1",
53
"identifier":"urn:stackpack:demo-stackpack:query-view:demo-customer-e",
54
"ownedBy":"urn:stackpack:demo-stackpack",
55
"eventTypes":[
56
​
57
],
58
"tags":[
59
​
60
],
61
"spanTypes":[
62
​
63
],
64
"_type":"QueryView"
65
}
Copied!

StackState UI

Check and propagation IDs

The ID for a check or propagation on a specific component can be found in in the StackState UI. These are the IDs for the component's instance of a check function or propagation function.
  1. 1.
    Click on a component to open the component details on the right of the screen.
  2. 2.
    Click on ... and select Show JSON.
  3. 3.
    Find the section for "checks" or "propagation".
  4. 4.
    Find the check or propagation that you want to enable logging for and copy the value from the field id.
Show JSON
  • Use the ID to enable logging for the component's check or propagation functions.

See also

Last modified 2mo ago