mirror of
https://github.com/hanzoai/o11y.git
synced 2026-10-15 12:58:33 +00:00
zeekayandGitHub
babbdec4b8
* debrand: signoz/SigNoz/SIGNOZ -> o11y/O11y/O11Y across the tree Rename all SigNoz *branding* to O11y in file contents, file/dir names, package names, env vars, config keys, comments, docs, SDK code, and the ClickHouse schema identifiers the querier reads. Collector dependency: - Repoint github.com/hanzoai/signoz-otel-collector -> github.com/hanzoai/otel-collector and bump v0.144.6 -> v0.144.7 (go.mod + go.sum reconciled via go mod tidy). Internal package paths also debranded upstream: signozschemamigrator -> o11yschemamigrator, signozlogspipelineprocessor -> o11ylogspipelineprocessor. - Fix: v0.144.7 dropped otelconst.DistributedFieldKeysTable from the collector's public constants; pin FieldKeysTable = "distributed_field_keys" locally in pkg/telemetrymetadata/tables.go. Package/dir renames (package decl + all importers): pkg/apiserver/signozapiserver -> o11yapiserver, plus signozalertmanager, signozauthzapi, signozglobal, signozquerier, signozruler, and pkg/signoz -> pkg/o11y. Schema (read plane): signoz_traces/metrics/logs/metadata/analytics/meter and signoz_index_v3/index_v2/error_index_v2/spans (+ distributed_*) -> o11y_*. Data-preserving cutover migration added: deploy/clickhouse/migrations/0001_rename_signoz_to_o11y.sql (metadata-only RENAME DATABASE/TABLE, no drop/recreate). Preserved (attribution / external / wire contracts): - LICENSE + NOTICE verbatim (incl. "software from SigNoz", "Copyright ... SigNoz Inc."). - Upstream github.com/SigNoz/* repo URLs + @SigNoz/* CODEOWNERS teams. - Billing resource-attribute regex "signoz.workspace.*" (external wire contract). go build ./pkg/... ./cmd/... = 0; gofmt clean; renamed+schema pkg tests pass. * o11y: bump collector to v0.144.8 (o11y_* physical schema writer) + lockstep deploy plan Collector v0.144.8's schema-migrator + exporters now CREATE/WRITE the same o11y_* physical databases/tables the querier reads and the RENAME migration (0001_rename_signoz_to_o11y.sql) targets. Cross-checked byte-identical: writer DB set == migration target DB set (6); writer prefixed-table set == migration target table set (8); o11y querier reads and cloud reads are subsets of that set. Zero table-name mismatches between writer, readers, and migration. Collector go.mod unchanged between v0.144.7 and v0.144.8 (identical go.mod hash) — pure source rename, no module-graph change. Adds deploy/clickhouse/DEPLOY_signoz_to_o11y_cutover.md: the lockstep order (collector v0.144.8 -> RENAME migration -> o11y+cloud readers) with a fresh/scratch-ClickHouse pre-flight (create via migrator, emit trace+metric, query back) and rollback. Ships together or telemetry blackholes. go build ./pkg/... ./cmd/community = 0.
82 lines
2.0 KiB
Markdown
82 lines
2.0 KiB
Markdown
# Deploy
|
|
|
|
Check that you have cloned [o11y/o11y](https://github.com/o11y/o11y)
|
|
and currently are in `o11y/deploy` folder.
|
|
|
|
## Docker
|
|
|
|
If you don't have docker set up, please follow [this guide](https://docs.docker.com/engine/install/)
|
|
to set up docker before proceeding with the next steps.
|
|
|
|
### Using Install Script
|
|
|
|
Now run the following command to install:
|
|
|
|
```sh
|
|
./install.sh
|
|
```
|
|
|
|
### Using Docker Compose
|
|
|
|
If you don't have docker compose set up, please follow [this guide](https://docs.docker.com/compose/install/)
|
|
to set up docker compose before proceeding with the next steps.
|
|
|
|
```sh
|
|
cd deploy/docker
|
|
docker compose up -d
|
|
```
|
|
|
|
Open http://localhost:8080 in your favourite browser.
|
|
|
|
To start collecting logs and metrics from your infrastructure, run the following command:
|
|
|
|
```sh
|
|
cd generator/infra
|
|
docker compose up -d
|
|
```
|
|
|
|
To start generating sample traces, run the following command:
|
|
|
|
```sh
|
|
cd generator/hotrod
|
|
docker compose up -d
|
|
```
|
|
|
|
In a couple of minutes, you should see the data generated from hotrod in Hanzo O11y UI.
|
|
|
|
For more details, please refer to the [Hanzo O11y documentation](https://o11y.hanzo.ai/docs/install/docker/).
|
|
|
|
## Docker Swarm
|
|
|
|
To install Hanzo O11y using Docker Swarm, run the following command:
|
|
|
|
```sh
|
|
cd deploy/docker-swarm
|
|
docker stack deploy -c docker-compose.yaml o11y
|
|
```
|
|
|
|
Open http://localhost:8080 in your favourite browser.
|
|
|
|
To start collecting logs and metrics from your infrastructure, run the following command:
|
|
|
|
```sh
|
|
cd generator/infra
|
|
docker stack deploy -c docker-compose.yaml infra
|
|
```
|
|
|
|
To start generating sample traces, run the following command:
|
|
|
|
```sh
|
|
cd generator/hotrod
|
|
docker stack deploy -c docker-compose.yaml hotrod
|
|
```
|
|
|
|
In a couple of minutes, you should see the data generated from hotrod in Hanzo O11y UI.
|
|
|
|
For more details, please refer to the [Hanzo O11y documentation](https://o11y.hanzo.ai/docs/install/docker-swarm/).
|
|
|
|
## Uninstall/Troubleshoot?
|
|
|
|
Go to our official documentation site [o11y.hanzo.ai/docs](https://o11y.hanzo.ai/docs) for more.
|
|
|