4 ms·

Is there any introduction to all the services that are included in the docker-compose file [1]? I wanted to give signoz a try, but the sheer amount of services

by ketzu 4y ago

Is there any introduction to all the services that are included in the docker-compose file [1]? I wanted to give signoz a try, but the sheer amount of services attached discouraged me, especially as I have to reconfigure them all to work with my setup. (Don't run them directly on the host, instead in a separated network, put the network interface behind traefik, figure out which access they need, provide all the configuration in a nice way without having to clone the full repo just to have the configuration files.) [1] https://github.com/SigNoz/signoz/blob/develop/deploy/docker/clickhouse-setup/docker-compose.yaml https://github.com/SigNoz/signoz/blob/develop/deploy/docker/...

rad_gruchalski 4y ago
Not associated with the project but a quick look suggests: a database (clickhouse), alertmanager, query-service, frontend are signoz components, otel* and hotrod are for distributed tracing. Otel stands for open telemetry (https://opentelemetry.io/ https://opentelemetry.io/), hotrod is a tracing demo app from jaeger: https://github.com/jaegertracing/jaeger/tree/main/examples/hotrod https://github.com/jaegertracing/jaeger/tree/main/examples/h.... Without thinking too much about it, I assume that: hotrod is a demo data source pushing traces to the otel collector, which stores data in clickhouse. Frontend fetches data from clickhouse using the query service. Alert manager probably looks at traces coming in and detects anomalies, so that you can get real-time alerts when things don’t look normal.
- ketzu 4y ago
  Thank you for the quick explanation, that helps a lot and gives me at least a starting point. Although sample services surprise me in the suggested docker-compose from the "how to install" section.
  - pranay01 4y ago
    yeah, it's not ideal - but we kept it to give users who are installing for the first time to get a hang of the product You can easily remove the sample services if you want - https://signoz.io/docs/operate/docker-standalone/#remove-the-sample-application https://signoz.io/docs/operate/docker-standalone/#remove-the...
pranay01 4y ago
The comment by rad_gruchalski is mostly accurate SigNoz has the following components - Frontend - ClickHouse (datastore) - Alert Manager (this is to monitor metrics and create alerts which you configure in SigNoz) - Query Service (which is the backend service which talks to datastore & frontend) - Otel collector ( which the collector provided by opentelemetry to collect telemetry data) The other two components for sample app which can be commented out - Hotrod ( which is a sample app) - load generator More details here - https://signoz.io/docs/architecture/#architecture-components https://signoz.io/docs/architecture/#architecture-components

by ketzu 4y ago

rad_gruchalski 4y ago

Not associated with the project but a quick look suggests: a database (clickhouse), alertmanager, query-service, frontend are signoz components, otel* and hotrod are for distributed tracing. Otel stands for open telemetry (https://opentelemetry.io/ https://opentelemetry.io/), hotrod is a tracing demo app from jaeger: https://github.com/jaegertracing/jaeger/tree/main/examples/hotrod https://github.com/jaegertracing/jaeger/tree/main/examples/h.... Without thinking too much about it, I assume that: hotrod is a demo data source pushing traces to the otel collector, which stores data in clickhouse. Frontend fetches data from clickhouse using the query service. Alert manager probably looks at traces coming in and detects anomalies, so that you can get real-time alerts when things don’t look normal.

ketzu 4y ago
Thank you for the quick explanation, that helps a lot and gives me at least a starting point. Although sample services surprise me in the suggested docker-compose from the "how to install" section.
- pranay01 4y ago
  yeah, it's not ideal - but we kept it to give users who are installing for the first time to get a hang of the product You can easily remove the sample services if you want - https://signoz.io/docs/operate/docker-standalone/#remove-the-sample-application https://signoz.io/docs/operate/docker-standalone/#remove-the...

pranay01 4y ago

The comment by rad_gruchalski is mostly accurate SigNoz has the following components - Frontend - ClickHouse (datastore) - Alert Manager (this is to monitor metrics and create alerts which you configure in SigNoz) - Query Service (which is the backend service which talks to datastore & frontend) - Otel collector ( which the collector provided by opentelemetry to collect telemetry data) The other two components for sample app which can be commented out - Hotrod ( which is a sample app) - load generator More details here - https://signoz.io/docs/architecture/#architecture-components https://signoz.io/docs/architecture/#architecture-components