mirror of
https://github.com/hanzoai/o11y.git
synced 2026-10-15 12:58:33 +00:00
zooqueen
e442dc6bd2
Verified against ghcr.io/hanzoai/datastore:26.6.1.1, the image these files run:
config /etc/datastore-server, data /var/lib/datastore, config root <datastore>,
client /usr/bin/datastore-client, and an entrypoint that reads DATASTORE_* and
nothing else. The mounts pointed at /etc/clickhouse-server and
/var/lib/clickhouse, which the image does not have, and passed CLICKHOUSE_* the
entrypoint ignores.
.devenv bound ${PWD}/../../../deploy/common/clickhouse/custom-function.xml; that
directory is deploy/common/datastore.
Service, hostname, volume, anchor and swarm-config names follow, and the cluster
XML replicas match the compose hostnames again.
The eight built-in integrations credited [email protected] and o11y.io, which
does not resolve; ours is o11y.hanzo.ai. The datastore integration is titled
Hanzo Datastore. Its id stays — an installed integration references it.
data-collected.json and the dashboards keep ClickHouseProfileEvents_* and
ClickHouseAsyncMetrics_*: those are the names the server binary emits, checked
in the running pod.
42 lines
1.7 KiB
XML
42 lines
1.7 KiB
XML
<?xml version="1.0"?>
|
|
<datastore>
|
|
<storage_configuration>
|
|
<disks>
|
|
<default>
|
|
<keep_free_space_bytes>10485760</keep_free_space_bytes>
|
|
</default>
|
|
<s3>
|
|
<type>s3</type>
|
|
<!-- For S3 cold storage,
|
|
if region is us-east-1, endpoint can be https://<bucket-name>.s3.amazonaws.com
|
|
if region is not us-east-1, endpoint should be https://<bucket-name>.s3-<region>.amazonaws.com
|
|
For GCS cold storage,
|
|
endpoint should be https://storage.googleapis.com/<bucket-name>/data/
|
|
-->
|
|
<endpoint>https://BUCKET-NAME.s3-REGION-NAME.amazonaws.com/data/</endpoint>
|
|
<access_key_id>ACCESS-KEY-ID</access_key_id>
|
|
<secret_access_key>SECRET-ACCESS-KEY</secret_access_key>
|
|
<!-- In case of S3, uncomment the below configuration in case you want to read
|
|
AWS credentials from the Environment variables if they exist. -->
|
|
<!-- <use_environment_credentials>true</use_environment_credentials> -->
|
|
<!-- In case of GCS, uncomment the below configuration, since GCS does
|
|
not support batch deletion and result in error messages in logs. -->
|
|
<!-- <support_batch_delete>false</support_batch_delete> -->
|
|
</s3>
|
|
</disks>
|
|
<policies>
|
|
<tiered>
|
|
<volumes>
|
|
<default>
|
|
<disk>default</disk>
|
|
</default>
|
|
<s3>
|
|
<disk>s3</disk>
|
|
<perform_ttl_move_on_insert>0</perform_ttl_move_on_insert>
|
|
</s3>
|
|
</volumes>
|
|
</tiered>
|
|
</policies>
|
|
</storage_configuration>
|
|
</datastore>
|