Skip to content

Commit a59a58f

Browse files
authored
Remove aggregation temporality enum and field. (#710)
1 parent c0a98a1 commit a59a58f

File tree

2 files changed

+5
-71
lines changed

2 files changed

+5
-71
lines changed

CHANGELOG.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,10 @@
44

55
The full list of changes can be found in the compare view for the respective release at <https://github.com/open-telemetry/opentelemetry-proto/releases>.
66

7+
### Removed
8+
9+
- profiles: remove aggregation temporality enum and field. [#710](https://github.com/open-telemetry/opentelemetry-proto/pull/710)
10+
711
## 1.8.0 - 2025-09-02
812

913
### Changed

opentelemetry/proto/profiles/v1development/profiles.proto

Lines changed: 1 addition & 71 deletions
Original file line numberDiff line numberDiff line change
@@ -308,80 +308,10 @@ message Link {
308308
bytes span_id = 2;
309309
}
310310

311-
// Specifies the method of aggregating metric values, either DELTA (change since last report)
312-
// or CUMULATIVE (total since a fixed start time).
313-
enum AggregationTemporality {
314-
/* UNSPECIFIED is the default AggregationTemporality, it MUST not be used. */
315-
AGGREGATION_TEMPORALITY_UNSPECIFIED = 0;
316-
317-
/** DELTA is an AggregationTemporality for a profiler which reports
318-
changes since last report time. Successive metrics contain aggregation of
319-
values from continuous and non-overlapping intervals.
320-
321-
The values for a DELTA metric are based only on the time interval
322-
associated with one measurement cycle. There is no dependency on
323-
previous measurements like is the case for CUMULATIVE metrics.
324-
325-
For example, consider a system measuring the number of requests that
326-
it receives and reports the sum of these requests every second as a
327-
DELTA metric:
328-
329-
1. The system starts receiving at time=t_0.
330-
2. A request is received, the system measures 1 request.
331-
3. A request is received, the system measures 1 request.
332-
4. A request is received, the system measures 1 request.
333-
5. The 1 second collection cycle ends. A metric is exported for the
334-
number of requests received over the interval of time t_0 to
335-
t_0+1 with a value of 3.
336-
6. A request is received, the system measures 1 request.
337-
7. A request is received, the system measures 1 request.
338-
8. The 1 second collection cycle ends. A metric is exported for the
339-
number of requests received over the interval of time t_0+1 to
340-
t_0+2 with a value of 2. */
341-
AGGREGATION_TEMPORALITY_DELTA = 1;
342-
343-
/** CUMULATIVE is an AggregationTemporality for a profiler which
344-
reports changes since a fixed start time. This means that current values
345-
of a CUMULATIVE metric depend on all previous measurements since the
346-
start time. Because of this, the sender is required to retain this state
347-
in some form. If this state is lost or invalidated, the CUMULATIVE metric
348-
values MUST be reset and a new fixed start time following the last
349-
reported measurement time sent MUST be used.
350-
351-
For example, consider a system measuring the number of requests that
352-
it receives and reports the sum of these requests every second as a
353-
CUMULATIVE metric:
354-
355-
1. The system starts receiving at time=t_0.
356-
2. A request is received, the system measures 1 request.
357-
3. A request is received, the system measures 1 request.
358-
4. A request is received, the system measures 1 request.
359-
5. The 1 second collection cycle ends. A metric is exported for the
360-
number of requests received over the interval of time t_0 to
361-
t_0+1 with a value of 3.
362-
6. A request is received, the system measures 1 request.
363-
7. A request is received, the system measures 1 request.
364-
8. The 1 second collection cycle ends. A metric is exported for the
365-
number of requests received over the interval of time t_0 to
366-
t_0+2 with a value of 5.
367-
9. The system experiences a fault and loses state.
368-
10. The system recovers and resumes receiving at time=t_1.
369-
11. A request is received, the system measures 1 request.
370-
12. The 1 second collection cycle ends. A metric is exported for the
371-
number of requests received over the interval of time t_1 to
372-
t_1+1 with a value of 1.
373-
374-
Note: Even though, when reporting changes since last report time, using
375-
CUMULATIVE is valid, it is not recommended. */
376-
AGGREGATION_TEMPORALITY_CUMULATIVE = 2;
377-
}
378-
379-
// ValueType describes the type and units of a value, with an optional aggregation temporality.
311+
// ValueType describes the type and units of a value.
380312
message ValueType {
381313
int32 type_strindex = 1; // Index into ProfilesDictionary.string_table.
382314
int32 unit_strindex = 2; // Index into ProfilesDictionary.string_table.
383-
384-
AggregationTemporality aggregation_temporality = 3;
385315
}
386316

387317
// Each Sample records values encountered in some program context. The program

0 commit comments

Comments
 (0)