@@ -48,14 +48,14 @@ To begin, create a configuration file named *applicationinsights.json*. Save it
48
48
"sampling" : {
49
49
"overrides" : [
50
50
{
51
- "telemetryKind " : " request" ,
51
+ "telemetryType " : " request" ,
52
52
"attributes" : [
53
53
...
54
54
],
55
55
"percentage" : 0
56
56
},
57
57
{
58
- "telemetryKind " : " request" ,
58
+ "telemetryType " : " request" ,
59
59
"attributes" : [
60
60
...
61
61
],
@@ -69,7 +69,7 @@ To begin, create a configuration file named *applicationinsights.json*. Save it
69
69
70
70
## How it works
71
71
72
- ` telemetryKind ` must be one of ` request ` , ` dependency ` , ` trace ` (log), or ` exception ` .
72
+ ` telemetryType ` must be one of ` request ` , ` dependency ` , ` trace ` (log), or ` exception ` .
73
73
74
74
When a span is started, the type of span and the attributes present on it at that time are used to check if any of the sampling
75
75
overrides match.
@@ -104,7 +104,7 @@ This will also suppress collecting any downstream spans (dependencies) that woul
104
104
"sampling" : {
105
105
"overrides" : [
106
106
{
107
- "telemetryKind " : " request" ,
107
+ "telemetryType " : " request" ,
108
108
"attributes" : [
109
109
{
110
110
"key" : " http.url" ,
@@ -131,7 +131,7 @@ This will suppress collecting telemetry for all `GET my-noisy-key` redis calls.
131
131
"sampling" : {
132
132
"overrides" : [
133
133
{
134
- "telemetryKind " : " dependency" ,
134
+ "telemetryType " : " dependency" ,
135
135
"attributes" : [
136
136
{
137
137
"key" : " db.system" ,
@@ -170,7 +170,7 @@ those will also be collected for all '/login' requests.
170
170
"sampling" : {
171
171
"overrides" : [
172
172
{
173
- "telemetryKind " : " request" ,
173
+ "telemetryType " : " request" ,
174
174
"attributes" : [
175
175
{
176
176
"key" : " http.url" ,
0 commit comments