Community
Participate
Working Groups
Default time correlation is not configurable. When log and trace data is correlated using the Default time correlation schema, the delta time is hard-coded to one second. This value is not always a useful indicator of an association between events. In order to be usable, this time should be customizable based on the data that is being correlated since the association between events is data-specific.
Looks like it's related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=83354. If not, provide more information on what you think should be modified and where, so that it can be triaged up to the right owner. Thanks!
*** This bug has been marked as a duplicate of 83354 ***
Closing.
Updating the target to reflect the iteration that this was closed in.
Reopening since defect #83354 is for handling clock skew between distributed log files and trace files. This defect is for configuring the default time value for the Default Time correlation schema.
Looks like it's for a correlation schema specialist. Are you one of those Eugene? If not, feel free to assign to the right person.
provides delta-time configurable field in TPTP preference page
Why do you need default delta time ? The delta time is at agent or node level. I think a better UI to set the delta time would be required instead. BTW the delta time is not hard-coded, it is user defined and we already have a place on the agent/node properties page where you can set it.
Marius, Paul is refering to the delta-time in the correlation, not the host/agent level one.
What do you mean by delta time in the correlation, I though we have only one delta time notion ?
that is the 'time-window' to determine if two events should be correlated.
Currently there is no such thing, and the default time correlation should always correlate by comparing the just adjusted time values (using the delta time). I propose to add a new correlation engine like "Similar time correlation" or a better name to add the function that you are talkin about, otherwise the user would be confused by the change in the behavior. The time threshold should be configurable at correlation time, so the user should be able to override the value from the preference, if you still need a preference.
I have already opened a feature some time ago to cover this scenario https://bugs.eclipse.org/bugs/show_bug.cgi?id=79605. I believe this current defect is a duplicate of the feature mentioned above.
mark this as dup of 79605, and rasie 79605 to be in 4.2 *** This bug has been marked as a duplicate of 79605 ***
