Hi, i'm new to Signoz, are there any documentation...
# general
e
Hi, i'm new to Signoz, are there any documentation on how to ingest windows event logs?
e
You might look at something like this: https://observiq.com/blog/monitoring-windows-events-with-opentelemetry Signoz is ultimately an OTEL inspector. That's not a very fair generalization, but for someone brand new to it, I think it's helpful to think about SigNoz as the query language and visualization layer to a database that was populated by OTEL
e
thank you, are there any documentation that had already achieved this on signoz? it would be nice to have this on the official documentation
e
I don't think it would be - it's just an OTEL producer
👍 2
The high level architecture is this: Any OTEL producer (APM metrics from your cloud app, logs, whatever. or even that article I sent you for producing OTEL data from windows events) ->[everything beoynd this point comes in the SigNoz stack but isn't necessarily created by the SigNoz team] SigNoz OTEL consumer (this is just a regular OTEL consumer/producer that takes OTEL events and stuffs them into the ClickHouse database) -> ClickHouse Then the SigNoz frontend can query the database (ClickHouse) to draw pretty graphs and set up alerts, etc.
n
yeah as Eric said you just need to add the receiver to the logs pipeline in your collector config, the configuration part will remain the same.
c
Here are the docs @Edryan Saltat - these should work for the self-hosted version of SigNoz. You'll have to modify the config file to include the windowseventlog receiver as mentioned by Eric and Nitya. https://signoz.io/docs/logs-management/send-logs/windows-events-log/
e
thank you so much for help! I appreciate the quick response in creating the documentation
c
Was the documentation able to resolve your query @Edryan Saltat?
e
I guess one thing, would it be possible to also provide documentation for self-hosted setups, just like with the other pages? thank you smuch
c
These should work for self-hosted setup as well with the only difference being that instead of creating a separated config.yaml file, you will have to update this file with the right set of receivers. Will add a separate section for Self-Hosted version soon.
👀 1