![]() ![]() See attached screenshot:Īs indicated on the image, take a screenshot of an alert with syscheck.mtime_before and syscheck.mtime_after fields on both Table and JSON tabs, and paste here, so we can see the timezone difference applied by Kibana (Elasticsearch store the real timestamp). We can see this if you click on a single Alert on Discover (with the syscheck fields), and the open the JSON tab. Aren't you getting this result when you modify the timezone? (For example, only the syscheck fileds being affected by the timezone change).Īnother thing that I would like to check is the raw JSON alert content. For more information, see Set your time zone. In GitLab 14.3 and earlier, users with no configured time zone default to the time zone configured at the instance level. New users must explicitly set their time zone before it displays on their profile. Now I can see that your browser timezone is in "Asia/Dhaka", so it's expected to see the same timestamps on the alerts on both "Browser" and "Asia/Dhaka".Īccording to my research, if you set a different timezone, all the date fields such as syscheck.mtime_before and syscheck.mtime_after will be affected by the setting. New users do not have a default time zone in GitLab 14.4 and later.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |