-
### Problem Statement
The windows_exporter and Grafana Alloy prometheus.exporter.windows do not allow to enable collectors if the infrastructure where windows_exporter/alloy is installed does not sup…
-
## **Description**
This issue is a section of #201, focuses on implementing the Windows Logcollector module in the Wazuh Agent 5.0.0. The Windows collector will utilize the Event Channel (eventchan…
-
### Problem Statement
Hi, not sure if its just me missing something here, but;
From what I can see, this mostly just pulls a bunch of cluster configurational settings. For example, I am busy using…
-
Our Windows integration currently supports the 'Forwarded Events' channel, whereby events from numerous Windows hosts can reside. As outlined in [this guide](https://ela.st/tj-qsg-wec) created by @Tho…
-
The only open source log collector in the market that can collect Windows logs remotely is Fluentd, with in_windows_eventlog2 plugin, that use https://github.com/fluent-plugins-nursery/winevt_c.
bu…
canob updated
2 weeks ago
-
### What's wrong?
Grafana Alloy is creating multiple bookmark files in `C:\ProgramData\GrafanaLabs\Alloy\data\loki.source.windowsevent.`
I would expect these files to merge into one `bookmark.xml` f…
-
### Component(s)
pkg/stanza
### Is your feature request related to a problem? Please describe.
This issue is created as a result of discussion in https://github.com/open-telemetry/opentelemetry-col…
-
### **Describe the bug**
Dashboard is mostly working as expected, seeing Audit Events and Event Code Analysis data. but no data displayed in Policy Review
###**Screen Shot
receiver/azureeventhub
### What happened?
## Description
The Azure service logs are unable to forward via OTel Collector.
## Steps to Reproduce
Add the receiver component in bui…