Data source catalog
Use this page when you opened Get Started to add a data source, or want to know which setup page covers what you want to monitor.
The data source catalog is the Get Started page, at /get-started. The old address,
/get-started-with-signoz-cloud, redirects to it.
It is organised by goal: you pick what you want to see in FuseScope, then the technology you use, and the entry opens the FuseScope setup page for it. Every entry ends up sending OpenTelemetry data over OTLP to your own FuseScope collector, with no ingestion key.
Monitor an application
Section titled “Monitor an application”Traces, metrics and logs from your services, for Services and the Traces explorer. Start with Instrument applications.
| Entry | Setup page |
|---|---|
| Java | Java |
| .NET | .NET |
| Node.js | Node.js |
| Python | Python |
| Go | Go |
| Ruby | Ruby |
| PHP | PHP |
| Web application (RUM) | Set up a web application |
Monitor AI and LLM calls
Section titled “Monitor AI and LLM calls”Model, tokens, cost and latency of LLM calls, for AI Observability.
| Entry | Setup page |
|---|---|
| Python (OpenAI, Anthropic, LangChain, …) | AI Observability for Python |
| Node.js (OpenAI, Anthropic, LangChain, …) | AI Observability for Node.js |
Collect logs
Section titled “Collect logs”Logs for the Logs explorer. Parse them afterwards with log pipelines.
| Entry | Setup page |
|---|---|
| Application logs (SDK) | Instrument applications › Logs |
| Log files | Logs from files |
| Kubernetes pods | Kubernetes logs |
| Syslog | Syslog |
| Fluent Bit, Fluentd | Fluent Bit and Fluentd |
Monitor infrastructure
Section titled “Monitor infrastructure”Hosts, clusters and metrics, for Infrastructure and the Metrics explorer.
| Entry | Setup page |
|---|---|
| Kubernetes | Kubernetes |
| Hosts (Linux VM, bare metal, Docker host) | Hosts |
| Prometheus metrics | Prometheus metrics |
Monitor a database or service
Section titled “Monitor a database or service”Integrations come with a collector configuration and ready-made dashboards.
| Entry | Setup page |
|---|---|
| ClickHouse | ClickHouse |
| MongoDB | MongoDB |
| Nginx | Nginx |
| PostgreSQL | PostgreSQL |
| Redis | Redis |
| AWS RDS MySQL | AWS RDS MySQL |
| AWS RDS PostgreSQL | AWS RDS PostgreSQL |
| AWS ElastiCache Redis | AWS ElastiCache Redis |
For anything else, such as Kafka or MySQL on your own servers, add its receiver from the collector-contrib receivers to a local collector.
Run a collector
Section titled “Run a collector”A collector next to your applications batches, retries and enriches data before it reaches FuseScope.
| Entry | Setup page |
|---|---|
| Docker | Collector on Docker |
| Linux VM (systemd) | Collector on a VM |
| An existing OpenTelemetry Collector | OTLP › From another collector |
Check that data arrives
Section titled “Check that data arrives”Within a minute of sending, look for the service under Services, or for the data in the Traces, Logs or Metrics explorers.