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.
The :new-page:`Splunk Distribution of OpenTelemetry Collector <https://docs.splunk.com/Observability/gdi/opentelemetry/deployment-modes.html>` supports proxies. You can configure proxies on each collector, or more typically, you would configure a collector in data forwarding (gateway) mode. In the gateway mode, you only need to configure the gateway collector(s) with the proxy settings; all other collectors can simply send data to the gateway collector.
31
+
The :new-page:`Splunk Distribution of OpenTelemetry Collector <https://docs.splunk.com/Observability/gdi/opentelemetry/deployment-modes.html>` supports proxies. You can configure proxies on each collector, or more typically, you would configure a collector in data forwarding (gateway) mode. In the gateway mode, you only need to configure the gateway collectors with the proxy settings; all other collectors can simply send data to the gateway collector.
32
32
33
33
Ensure that you give the Splunk Distribution of OpenTelemetry Collector the ability to resolve the network names and make outbound HTTPS network connections to the URLs listed in :ref:`allow-urls` or the domains listed in :ref:`allow-domains`. Verify also the list of :ref:`exposed ports and endpoints <otel-exposed-endpoints>`.
Copy file name to clipboardExpand all lines: data-visualization/charts/export-and-share-charts.rst
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Export chart contents
16
16
17
17
For line charts, area charts, and column charts, you can export the chart contents to a CSV file. The most recent 100 data points will be exported, along with the values of the dimensions associated with them.
18
18
19
-
To export a chart, first select :strong:`Data table` tab, next select :strong:`Export as CSV` download icon in the table headers row on the last column (the right side corner).
19
+
To export a chart, first select :guilabel:`Data table` tab, next select :guilabel:`Export as CSV` download icon in the table headers row on the last column (the right side corner).
20
20
21
21
.. note:: List charts and table charts can't be exported because they don't have a data table.
22
22
@@ -38,7 +38,7 @@ The techniques available for sharing a chart depend on where you are viewing the
38
38
- :strong:`Notes`
39
39
40
40
* - In the Chart Builder
41
-
- Use the Share icon at top right or select :strong:`Share` from the chart's Actions menu (|more|)
41
+
- Use the Share icon at top right or select :guilabel:`Share` from the chart's Actions menu (|more|)
42
42
- Version you are viewing, including any unsaved changes
43
43
- URL that links to a copy of the chart, which you can send to others (see :ref:`share-feature-to-share`) or :ref:`pasting-chart-url-into-slack`
44
44
- In most cases, can be viewed only by other users
@@ -56,7 +56,7 @@ The techniques available for sharing a chart depend on where you are viewing the
56
56
- Can be viewed by anyone
57
57
58
58
* - On a dashboard
59
-
- Select :strong:`Share` from the chart's Action menu (|more|)
59
+
- Select :guilabel:`Share` from the chart's Action menu (|more|)
60
60
- Most recently saved version
61
61
- URL that links to a copy of the chart, which you can send to others (see :ref:`share-feature-to-share`) or :ref:`pasting-chart-url-into-slack`
62
62
- In most cases, can be viewed only by other users
@@ -68,7 +68,7 @@ The techniques available for sharing a chart depend on where you are viewing the
68
68
- Can be viewed only by other users
69
69
70
70
* -
71
-
- Select :strong:`Download chart as image` from the chart's Actions menu
71
+
- Select :guilabel:`Download chart as image` from the chart's Actions menu
72
72
- Most recently saved version
73
73
- Provides a graphic representation of the chart
74
74
- Can be viewed by anyone
@@ -91,9 +91,9 @@ Use the Share feature to share a chart
91
91
92
92
You can share a copy of a chart. Copies include unsaved changes at the time you share, and autoexpire unless the recipient saves them. Sharing a copy is perfect for when you make a change that you want to show your team members, but don't want to modify the original chart.
93
93
94
-
- To share a chart you are viewing in the Chart Builder, select the :strong:`Share` icon near the upper right corner of the chart or select :strong:`Share` from the chart's Actions menu (|more|).
94
+
- To share a chart you are viewing in the Chart Builder, select the :guilabel:`Share` icon near the upper right corner of the chart or select :guilabel:`Share` from the chart's Actions menu (|more|).
95
95
96
-
- To share a chart you are viewing in a dashboard, select :strong:`Share` from the chart's Actions menu (|more|).
96
+
- To share a chart you are viewing in a dashboard, select :guilabel:`Share` from the chart's Actions menu (|more|).
97
97
98
98
You'll see options for sharing, discussed below.
99
99
@@ -104,7 +104,7 @@ Share a copy directly from Infrastructure Monitoring
104
104
105
105
You can send a copy of the chart to an email address or to any available third-party services (See :ref:`admin-notifs-index`.).
106
106
107
-
After adding recipients, select :strong:`Share`. Recipients receive a link to the copy. When they open it, they can edit and save their copy without affecting the original.
107
+
After adding recipients, select :guilabel:`Share`. Recipients receive a link to the copy. When they open it, they can edit and save their copy without affecting the original.
108
108
109
109
.. caution::
110
110
@@ -116,7 +116,7 @@ After adding recipients, select :strong:`Share`. Recipients receive a link to th
116
116
Share a copy by using a link
117
117
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
118
118
119
-
You might want to send out a personal email or post a link to the copy on an internal website. To do this, select :strong:`Copy`. Only members of your organization with a login will be able to see the chart you share.
119
+
You might want to send out a personal email or post a link to the copy on an internal website. To do this, select :guilabel:`Copy`. Only members of your organization with a login will be able to see the chart you share.
"Splunk Observability Cloud implements multiwindow, multi-burn-rate alerting to let you know when the rate of consumption of your service level objective (SLO) error budget exceeds a healthy burn rate threshold for the "
"While you have always been able to use the data in Splunk Observability Cloud to monitor, troubleshoot, and optimize your services, SLO management provides a quantitative way to track the reliability and performance "
338
-
"ofyourservices. This allows teams to make the right investment trade-offs between product development and operational work."
338
+
"of your services. This allows teams to make the right investment trade-offs between product development and operational work."
"Service level monitoring is the process of measuring, tracking, and analyzing a variety of service level indicators (SLIs) associated with a given service. This process calculates the health of a deployed software or "
350
-
"serviceandcompares it against the servicelevel agreement (SLA)."
350
+
"service and compares it against the service-level agreement (SLA)."
"A measurement of how your SLI performs relative to your SLO over a period of time. Error budget measures the difference between actual and desired performance. It determines how unreliable your service might be "
422
-
"duringthisperiod and serves as a signal when you need to take corrective action."
422
+
"during this period and serves as a signal when you need to take corrective action."
"A unitless measurement of how quickly a service consumes the error budget during the compliance window of the SLO. Burn rate makes the SLO and error budget actionable, showing service owners when a current incident "
0 commit comments