This question was created in reference to: [Horde node warnings affecting suspect commit calculation on [Content removed]
Hello,
We are running data validation that can surface warnings, and we’ve had multiple warnings active for several days.
When a new build health issue is created for a newly introduced warning while other warnings already exist, the suspect range starts from the last green CL (from a few days ago), even though the new warning first appeared today.
Is this intended behavior?
I’ve referenced a thread discussing a similar topic, but I’m not sure if it applies to this exact scenario.
Thank you.
Hello, are these “Hashed” issues, you can tell both in the build health issue modal, as well as the issue history view available off the model, which is an audit of what is going on with the issues.
Hashed issues operate at the step level, and aggressively group, otherwise the volume of issues quickly explodes. The hashing does some redactions for things like timestamps and memory addressed, though is in general aggressive. It is the default and last resort, and you are much better off using structured logging, and events..
You can use structured logging directly, and there are also many examples of log event matchers under EpicGames.LogMatchers/ for logging which isn’t under control, to add event information. Also, looking at the handlers might give some better insight how these are used to group, a good example is the EpicGames.Horde/Issues/Handlers/GauntletIssueHandler.cs, you can also see the hashed issue handler under that directory.
Though I am guessing the root of this is the hashed issues, which can group across steps.