ockam_api 0.93.0

Ockam's request-response API
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

use chrono::{DateTime, Utc};
use ockam_core::OpenTelemetryContext;
use std::time::SystemTime;

/// A journey is a pseudo-trace where spans represents user events.
/// The tracing context is kept in the `opentelemetry_context` field.
///
/// A journey is time-limited to avoid spans accumulating for too long in a single trace.
/// After a while a new Journey is started and its `previous_opentelemetry_context` field must
/// point to the previous journey.
#[derive(Debug, Clone, PartialEq, Eq)]
pub struct Journey {
    opentelemetry_context: OpenTelemetryContext,
    previous_opentelemetry_context: Option<OpenTelemetryContext>,
    start: DateTime<Utc>,
}

impl Journey {
    pub fn new(
        opentelemetry_context: OpenTelemetryContext,
        previous_opentelemetry_context: Option<OpenTelemetryContext>,
        start: DateTime<Utc>,
    ) -> Journey {
        Journey {
            opentelemetry_context,
            previous_opentelemetry_context,
            start,
        }
    }

    pub fn opentelemetry_context(&self) -> OpenTelemetryContext {
        self.opentelemetry_context.clone()
    }

    pub fn previous_opentelemetry_context(&self) -> Option<OpenTelemetryContext> {
        self.previous_opentelemetry_context.clone()
    }

    pub fn start(&self) -> DateTime<Utc> {
        self.start
    }

    pub fn start_system_time(&self) -> SystemTime {
        SystemTime::from(self.start)
    }

    pub fn extract_context(&self) -> opentelemetry::Context {
        self.opentelemetry_context.extract()
    }
}