Defining API Token on First Run Using Environment Variables
TLDR Kaan inquires about defining an API token on first run using environment variables. Prabhat confirms it is not yet possible and suggests creating an issue for it.
Prabhat
Mon, 19 Jun 2023 20:42:50 UTCNot yet.
Kaan
Mon, 19 Jun 2023 20:46:15 UTCThank you.
Prabhat
Mon, 19 Jun 2023 21:04:25 UTCCan you create an issue for it, so we can prioritize it. I am hearing this kind of requirement second time.
OpenObserve
Indexed 419 threads
OpenObserve is an open-source, petabyte-scale observability platform for the cloud native realm, offering a 10x cost reduction and 140x less storage use compared to competitors like Elasticsearch or Splunk. Built in Rust for exceptional performance, it offers comprehensive features like logs, metrics, traces, dashboards, and more | Knowledge Base powered by Struct.AI
View in AppSimilar Threads
Configuring Key/Token/Password for Log Ingestion in OpenObserve
Integrating OpenObserve with a User Solution and Handling Errors.
LDAP Support, Metrics Separation, and Ingestion Token Concerns
ZincObserve Installation Issue - Email and Env variables
Troubleshooting openobserve HA Self-hosted Set Up Error
Kaan
Mon, 19 Jun 2023 20:42:11 UTCHello, is it possible to define an api token on first run using environment variables? One usecase I have is getting some machines up and ready, directly communicating with an OpenObserve on the same stack. I can define root user and password but not token for API authentication