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
Copy file name to clipboardExpand all lines: exporter/opentelemetry-exporter-prometheus-remote-write/README.rst
+17-16
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,6 @@ Table of Contents
42
42
43
43
- `Supported Aggregators`_
44
44
- `Error Handling`_
45
-
- `Retry Logic`_
46
45
- `Contributing`_
47
46
48
47
- `Design Doc`_
@@ -170,23 +169,28 @@ and key files in the ``tls_config`` parameter.
170
169
171
170
Supported Aggregators
172
171
---------------------
172
+
Behaviour of these aggregators is outlined in the OpenTelemetry Specification `here <https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/metrics/api.md#aggregations>`_.
173
173
174
174
- Sum
175
175
- MinMaxSumCount
176
176
- Histogram
177
177
- LastValue
178
178
- ValueObserver
179
179
180
+
All aggregators are converted into the `timeseries` data format. However, the
181
+
structure in which they are converted differs from aggregator to aggregator. A
182
+
map of the conversion methods can be found `here <https://github.com/open-telemetry/opentelemetry-python-contrib/blob/master/exporter/opentelemetry-exporter-prometheus-remote-write/src/opentelemetry/exporter/prometheus_remote_write/__init__.py#L75>`_.
183
+
Details on how the conversion is being done can be found `here <https://github.com/open-telemetry/opentelemetry-python-contrib/blob/master/exporter/opentelemetry-exporter-prometheus-remote-write/src/opentelemetry/exporter/prometheus_remote_write/__init__.py#L196>`_
184
+
180
185
Error Handling
181
186
--------------
182
187
183
188
In general, errors are raised by the calling function. The exception is
184
189
for failed requests where any error status code is logged as a warning
185
190
instead.
186
191
187
-
This is because the exporter does not implement any retry logic as it
188
-
sends cumulative metrics data. This means that in the long-term data will be preserved
189
-
even if failed exports are dropped in the interim.
192
+
This is because the exporter does not implement any retry logic as data that
193
+
failed to export will be dropped.
190
194
191
195
For example, consider a situation where a user increments a Counter
192
196
instrument 5 times and an export happens between each increment. If the
@@ -203,8 +207,6 @@ Then the received data will be:
203
207
204
208
1 4 5
205
209
206
-
The end result (metric value 5) is the same since the aggregations are cumulative
207
-
208
210
Contributing
209
211
------------
210
212
@@ -219,15 +221,6 @@ Design Doc
219
221
This document is stored elsewhere as it contains large images which will
0 commit comments