Files
openobserve/src/api_management
Huaijin e236c7e653 refactor: extract database layer into db crate (#13340)
## Summary

- extract persistence, cache, watcher data access, and DB service
modules from openobserve-core into a standalone workspace db crate
- keep application orchestration that depends on search, organization
provisioning, and other Core services behind the existing Core db facade
- preserve existing call paths through re-exports while making the
dependency direction openobserve-core -> db
- move HTTP error mapping back to the Core/API boundary so db has no
direct axum dependency
- avoid provider/provisioner callback traits and function-pointer hooks

## Validation

- cargo fmt --all
- cargo check --all-targets
- cargo check -p db --all-targets
- Enterprise workspace: cargo check --all-targets --offline
- Enterprise workspace: cargo check -p db --all-targets --features
enterprise --offline

Companion Enterprise manifest PR: openobserve/o2-enterprise#2230.
2026-07-22 07:21:34 +00:00
..

openobserve-api-management

openobserve-api-management contains the management and control-plane HTTP APIs for OpenObserve.

It includes handlers and models for areas such as alerts, templates, destinations, organizations, users, authorization, dashboards, and folders, together with authentication helpers.

The crate depends on openobserve-api-common for shared HTTP types and openobserve-core for application services. It does not depend on the query API crate. Routing and top-level OpenAPI composition remain in openobserve-api.

This is an internal workspace crate and is not published independently.