You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: apm/apm-spans-traces/traces-spans.rst
+21-23Lines changed: 21 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,19 +39,19 @@ Spans and traces form the backbone of application monitoring in Splunk APM. Use
39
39
40
40
41
41
.. raw:: html
42
+
43
+
<embed>
44
+
<h2>What are services?<aname="what-are-services"class="headerlink"href="#what-are-services"title="Permalink to this headline">¶</a></h2>
45
+
</embed>
42
46
43
-
<embed>
44
-
<h2>What are services?</h2>
45
-
</embed>
46
47
47
48
Services are the key components of the systems you can monitor with Splunk APM.
48
49
49
-
50
50
.. raw:: html
51
-
52
-
<embed>
53
-
<h2>What are traces and spans?</h2>
54
-
</embed>
51
+
52
+
<embed>
53
+
<h2>What are traces and spans?<aname="what-are-traces-spans"class="headerlink"href="#what-are-traces-spans"title="Permalink to this headline">¶</a></h2>
54
+
</embed>
55
55
56
56
57
57
A trace is a collection of operations that represents a unique transaction handled by an application and its constituent services. A span represents a single operation within a trace.
@@ -66,13 +66,11 @@ The following image illustrates the relationship between traces and spans:
66
66
67
67
A span might refer to another span as its parent, indicating a relationship between operations involved in the trace. In the preceding image, span A is a parent span, and span B is a child span. This relationship might indicate that, for example, span A makes a service call that triggers the operation captured by span B. In this image, span C is also a child of span B, and so on.
68
68
69
-
70
69
.. raw:: html
71
-
72
-
<embed>
73
-
<h2>Span metadata</h2>
74
-
</embed>
75
-
70
+
71
+
<embed>
72
+
<h2>Span metadata<aname="span-metadata"class="headerlink"href="#span-metadata"title="Permalink to this headline">¶</a></h2>
73
+
</embed>
76
74
77
75
Each span contains metadata about the operation captured by the span and the service in which the operation took place.
78
76
@@ -117,12 +115,11 @@ Each span contains the following basic metadata:
117
115
- Delay between the start of the parent trace and the start of this particular span
118
116
119
117
120
-
121
118
.. raw:: html
122
-
123
-
<embed>
124
-
<h2>Span tags</h2>
125
-
</embed>
119
+
120
+
<embed>
121
+
<h2>Span tags<aname="span-tags"class="headerlink"href="#span-tags"title="Permalink to this headline">¶</a></h2>
122
+
</embed>
126
123
127
124
128
125
Span tags are key-value pairs that provide additional information and context about the operations a span represents. Both the keys and values are strings, and span tag keys for a single span must be unique. You can use span tags to query and filter traces, or to get information about the spans of a trace during troubleshooting.
@@ -133,11 +130,12 @@ Span tags are most useful when they follow a simple, dependable system of naming
133
130
134
131
.. note:: Span tags in Splunk APM are distinct from metadata tags in Splunk Infrastructure Monitoring, which are searchable labels or keywords you can assign to metric dimensions in the form of strings rather than as key-value pairs. To learn more about metadata tags, see :ref:`metadata-infra-tags`.
135
132
136
-
.. raw:: html
137
133
138
-
<embed>
139
-
<h2>Identities</h2>
140
-
</embed>
134
+
.. raw:: html
135
+
136
+
<embed>
137
+
<h2>Identities<aname="identities"class="headerlink"href="#identities"title="Permalink to this headline">¶</a></h2>
138
+
</embed>
141
139
142
140
An identity represents a unique set of indexed span tags for a Splunk APM object, and always includes at least one service.
Copy file name to clipboardExpand all lines: sp-oncall/notifications/notification-types.rst
+29-31Lines changed: 29 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,10 +30,10 @@ You can also configure delayed notifications for alerts that may auto-resolve wi
30
30
31
31
32
32
.. raw:: html
33
-
34
-
<embed>
35
-
<h2>Push notification</h2>
36
-
</embed>
33
+
34
+
<embed>
35
+
<h2>Push notification<aname="push-notification"class="headerlink"href="#push-notification"title="Permalink to this headline">¶</a></h2>
36
+
</embed>
37
37
38
38
39
39
Push notifications are sent through the application. We use push for:
@@ -46,69 +46,67 @@ Push notifications are sent through the application. We use push for:
46
46
When a push notification is used to deliver a page, you will have the option to acknowledge, reroute, or snooze the incident straight from the notification.
47
47
48
48
.. image:: /_images/spoc/notif-types1.png
49
-
:width:100%
49
+
:width:35%
50
50
:alt:Splunk On-Call push notification.
51
51
52
-
53
52
.. raw:: html
54
-
55
-
<embed>
56
-
<h2>SMS</h2>
57
-
</embed>
53
+
54
+
<embed>
55
+
<h2>SMS<aname="sms"class="headerlink"href="#sms"title="Permalink to this headline">¶</a></h2>
56
+
</embed>
58
57
59
58
SMS notifications can be used in your personal paging policy. The message you receive is, at most, 160 characters, and it displays the
60
59
incident number, entity_display_name, and response code if two-way SMS is supported. When you receive an SMS notification, two codes are included in the message so you can acknowledge aor resolve the alert by responding with the correct five-digit code. These response codes expire after 1 hour.
61
60
62
61
.. image:: /_images/spoc/notif-types2.png
63
-
:width:100%
62
+
:width:35%
64
63
:alt:Splunk On-Call SMS notification.
65
64
66
-
67
65
.. raw:: html
68
-
69
-
<embed>
70
-
<h2>SMS Subscription Management</h2>
71
-
</embed>
66
+
67
+
<embed>
68
+
<h3>SMS Subscription Management<aname="sms-subscription"class="headerlink"href="#sms-subscription"title="Permalink to this headline">¶</a></h3>
69
+
</embed>
72
70
73
71
You may stop and start our SMS notification subscription by replying to the message with STOP or START. Although, it is best to manage your notifications from the personal profile page in Splunk On-Call.
74
72
75
73
.. raw:: html
76
-
77
-
<embed>
78
-
<h2>WhatsApp</h2>
79
-
</embed>
74
+
75
+
<embed>
76
+
<h2>WhatsApp<aname="whatsapp"class="headerlink"href="#whatsapp"title="Permalink to this headline">¶</a></h2>
77
+
</embed>
80
78
81
79
You can use WhatsApp notifications in your personal paging policy. To enable WhatsApp, download and configure the WhatsApp application from the Apple App Store or Google Play Store. Next, access your user profile in Splunk On-Call and enter and verify your mobile number. After verification, an :guilabel:`Enable WhatsApp` button will appear next to the number and you'll be able to use WhatsApp in your Paging Policy.
82
80
83
81
.. raw:: html
84
-
85
-
<embed>
86
-
<h2>Email</h2>
87
-
</embed>
82
+
83
+
<embed>
84
+
<h2>Email<aname="email"class="headerlink"href="#email"title="Permalink to this headline">¶</a></h2>
85
+
</embed>
88
86
89
87
Emails can be used for pages. Emails can also be used as reminders that your Splunk On-Call instance is in :ref:`maintenance-mode`, or that you have a gap in your schedule due to a :ref:`scheduled-overrides` that is not covered.
0 commit comments