I have added one more collector to the JS tracker, but snowplow tracker is behaving strange.
What it is doing,
For example if three events are meant for each collector, what it is doing after first event all events are going to recently second collector.
did anybody faced this kind of issue, while adding one more collector to existing tracker?
There is observation, i want to share:
we have a main collector (C1) which is of https type,
when C2 collector was of http type, it was working smooth.
but when C2 collector changed to https type, this error came up.
I’ve certainly never seen this happen before. One thing to perhaps check, are your network requests all succeeding in your browser? I’m curious if one is failing (due to https or something) and then maybe it’s retrying but to the wrong collector (that’d be a bug but 2.9.0 is rather old now).
Also, is the namespace array in your tracking example 100% the same values as cname you’ve used in the newTracker calls? I ask as cname is a concatenation of three strings so it looks like some potential for a mismatch there.
Could you check your localstorage queue names? You should have a queue for each tracker namespace you’ve created.
I’m a bit baffled as to why you’re seeing this behaviour if I’m honest, I think the http to https switch is a red herring as that shouldn’t have any impact if you aren’t seeing any failing network requests (to be honest, even if you were the tracker shouldn’t be sending events to the wrong collector).
I’m thinking it might be worth removing some of the complexity from your tracker set up just to rule out any programming errors.