Roland Huß 5a2bfd6ad5 refactor: Replace SQLITE_DB_PATH by SQLITE_STORE_DIR env in templates (#2055) ... # What does this PR do? The telemetry provider configs is the only one who leverages the env var `SQLITE_DB_PATH` for pointing to persistent data in the respective templates, whereas usually `SQLITE_STORE_DIR` is used. This PR modifies the `sqlite_db_path` in various telemetry configuration files to use the environment variable `SQLITE_STORE_DIR` instead of `SQLITE_DB_PATH`. This change ensures that _only_ the SQLITE_STORE_DIR needs to be set to point to a different persistence location for providers. All references to `SQLITE_DB_PATH` have been removed. Another improvement could be to move `sqlite_db_path` to `db_path` in the telemetry provider config, to align with the other provider configurations. That could be done by another PR (if wanted).		2025-04-29 15:28:10 -07:00
..
__init__.py	chore: mypy violations cleanup for inline::{telemetry,tool_runtime,vector_io} (#1711)	2025-03-20 10:01:10 -07:00
config.py	refactor: Replace SQLITE_DB_PATH by SQLITE_STORE_DIR env in templates (#2055)	2025-04-29 15:28:10 -07:00
console_span_processor.py	chore: mypy violations cleanup for inline::{telemetry,tool_runtime,vector_io} (#1711)	2025-03-20 10:01:10 -07:00
sqlite_span_processor.py	feat: use same trace ids in stack and otel (#1759)	2025-03-21 15:41:26 -07:00
telemetry.py	feat: introduce llama4 support (#1877)	2025-04-05 11:53:35 -07:00