Hi, I want to love this product. This will be the 3rd or 4th time I have looked at the docs to figure out basic setup.

Each time I look into this. I look to see how it can report CPU/Memory/Disk of the systems at large. When I read, all I find on open telemetry and SigNoz is how to integrate with application stacks.

Am I missing something fundamental in that SygNoz/OpenTelemetry do not integrate with host level metrics? I really, really want to use this product. But this extremely BASIC implementation to use the service is 100% missing for documentation as far as I can tell. Even the example page has nothing listed https://signoz.io/docs/tutorials/ ...

So I am either trying to find out how to make SygNoz do something it was not built to do... or the documentation has a huge hole in it.

Let me know how to proceed, if you have time. It's appreciated so that I dont keep walking down the wrong road and hoping to find something useful.

Thanks!

Hey, thanks for writing. Our initial focus was on application monitoring - that is why docs are more oriented towards it. But I can understand you may find it tough to understand for infra metrics (CPU/Memory/Disk)

As of now, there are couple of ways to do this: 1. You can enable hostmetrics receiver in opentelemetry collector 2. You can use something like prometheus node exporter and enable prometheus receiver in opentelemetry collector

If you follow this for a VM setup, you should be able to get your host metrics - https://signoz.io/docs/userguide/send-metrics/#enable-a-spec...

If you are on k8s, check out this - https://signoz.io/docs/tutorial/kubernetes-infra-metrics/

If it is still confusing, do drop by in our slack community ( https://signoz.io/slack) We are quite active there and should be able to help you get started

Many thanks. I took notice of your prometheus mention and had also seen that peppered in the docs for both services (openT and SigN) as a way to gather data.

As time investment is a dangerous thing I didn't plop myself down for some R&D... But... thanks to your post I'll have another go at it and determine how to get it to hum.

Thanks again!

Awesome! Do let us know if you face any issues, should be fairly simple to do. We are on slack at https://signoz.io/slack if you need any help

Question: Is it licensed under MIT? The license reads as it could be MIT but there is no reference to it.

The ee/ folder is under proprietary license. Rest of the code is under MIT license

Thanks for the response. I've realized that the license between the branch develop and main is not the same at the moment.

Does not match the file I see when clicking "View License", e.g. will not match the LICENSE file the next release may have?

https://github.com/SigNoz/signoz/blob/develop/LICENSE

yes, upcoming release will have license which is currently in `develop` branch

I tried installation on Windows 10 via Rancher-Desktop using "other platform" docs but ran into issues with dependencies on sh/bash. Are there any windows specific instructions?

hey, windows is not officially supported. If you have a Ubuntu machine/Mac, you can try in that

https://signoz.io/docs/install/docker/#prerequisites

Gotcha, thanks. Do the linux instructions work on any WSL distro?

I got it running on WSL w/ docker using docker compose. I didn’t do much more than get it running though.

Awesome! Let us know if you have nay feedback when you get a chance to dive deeper. Here's our slack community- https://signoz.io/slack

How are you dealing with join's in clickhouse? Do you just avoid them all together?

We use clickhouse at Luabase and join performance is the only weak point we've hit.

Yes...we are avoiding join altogether. Currently we used join in timeseries but we are probably moving away from that due to perf. Single table is amazingly fast