You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had an issue where our AWS wodles were unable to connect to our S3 buckets for a few weeks. This happened after an upgrade from 4.5 to 4.7 and the AWS authentication method apparently changed.
We fixed the issue and Wazuh started reading the buckets and loading events. However, the events then show up in the dashboard with a time value of when they were ingested and not when the event occurred. Normally, when all is going well, these are within a few minutes of each other but, in this case, it can be several days apart:
It would be very useful to have the ability to change the time column on the events page to use a different date/time field from the events.
We've thought of trying to create a filter on data.aws.eventTime but the dashboard seems to treat it as a text value rather than a date and does not present range options such as after, before or between
The text was updated successfully, but these errors were encountered:
We had an issue where our AWS wodles were unable to connect to our S3 buckets for a few weeks. This happened after an upgrade from 4.5 to 4.7 and the AWS authentication method apparently changed.
We fixed the issue and Wazuh started reading the buckets and loading events. However, the events then show up in the dashboard with a time value of when they were ingested and not when the event occurred. Normally, when all is going well, these are within a few minutes of each other but, in this case, it can be several days apart:
It would be very useful to have the ability to change the time column on the events page to use a different date/time field from the events.
We've thought of trying to create a filter on data.aws.eventTime but the dashboard seems to treat it as a text value rather than a date and does not present range options such as after, before or between
The text was updated successfully, but these errors were encountered: