/*
* server
*
* ## Real-time data The only real-time path to get tracing data is to ingest via OpenTelemetry (`POST /api/public/otel/v1/traces`) and retrieve via Observations API v2 (`GET /api/public/v2/observations`) and Metrics API v2 (`GET /api/public/v2/metrics`). Other public API write and read endpoints can delay data by about 10 minutes. Direct OpenTelemetry exporters must send the `x-langfuse-ingestion-version: 4` header; current Python and JS SDKs already do. See the [Public API docs](https://langfuse.com/docs/api-and-data-platform/features/public-api) and [real-time ingestion](https://langfuse.com/integrations/native/opentelemetry.md#real-time-ingestion). ## Authentication Authenticate with the API using [Basic Auth](https://en.wikipedia.org/wiki/Basic_access_authentication), get API keys in the project settings: - username: Langfuse Public Key - password: Langfuse Secret Key ## Exports - OpenAPI spec: https://cloud.langfuse.com/generated/api/openapi.yml - Self-hosted deployments: interactive API reference at `/api/docs` and OpenAPI spec at `/api/openapi.yaml`
*
* The version of the OpenAPI document:
*
* Generated by: https://openapi-generator.tech
*/
use crate::models;
use serde::{Deserialize, Serialize};
/// BlobStorageSyncStatus : Sync status of the blob storage integration: - `disabled` — integration is not enabled - `error` — last export failed (see `lastError` for details) - `running` — an export job is currently being processed - `queued` — next export is overdue (`nextSyncAt` is in the past) and waiting to be picked up by the worker - `idle` — enabled but has never exported yet and no export is queued - `up_to_date` — all available data has been exported; next export is scheduled for the future **ETL usage**: poll this endpoint and check for `up_to_date` status. Compare `lastSyncAt` against your ETL bookmark to determine if new data is available. Note that exports run with a 20-minute lag buffer, so `lastSyncAt` will always be at least 20 minutes behind real-time.
/// Sync status of the blob storage integration: - `disabled` — integration is not enabled - `error` — last export failed (see `lastError` for details) - `running` — an export job is currently being processed - `queued` — next export is overdue (`nextSyncAt` is in the past) and waiting to be picked up by the worker - `idle` — enabled but has never exported yet and no export is queued - `up_to_date` — all available data has been exported; next export is scheduled for the future **ETL usage**: poll this endpoint and check for `up_to_date` status. Compare `lastSyncAt` against your ETL bookmark to determine if new data is available. Note that exports run with a 20-minute lag buffer, so `lastSyncAt` will always be at least 20 minutes behind real-time.
#[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)]
pub enum BlobStorageSyncStatus {
#[serde(rename = "idle")]
Idle,
#[serde(rename = "running")]
Running,
#[serde(rename = "queued")]
Queued,
#[serde(rename = "up_to_date")]
UpToDate,
#[serde(rename = "disabled")]
Disabled,
#[serde(rename = "error")]
Error,
}
impl std::fmt::Display for BlobStorageSyncStatus {
fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result {
match self {
Self::Idle => write!(f, "idle"),
Self::Running => write!(f, "running"),
Self::Queued => write!(f, "queued"),
Self::UpToDate => write!(f, "up_to_date"),
Self::Disabled => write!(f, "disabled"),
Self::Error => write!(f, "error"),
}
}
}
impl Default for BlobStorageSyncStatus {
fn default() -> BlobStorageSyncStatus {
Self::Idle
}
}