store_lookups: not parsing all values in subsequent call about nri-flex

[bpschmitt]

Update: so far it looks good. I want to do some more testing before I call this Closed but it looks promising. Thanks again for the quick turnaround!

[Kav91]

I think the issue here is because there is more then one lookup in the url.

When I do a single lookup it appears to work as intended.

With multiple it just attempts the second lookup with the value from the same index of the first lookup.

Will take a look at supporting multi-lookups.

[Kav91]

@bpschmitt can you give this a go again on the latest version and see how you go?

It should make the needed requests, but we may need to filter out some unneeded events that are generated.

[bpschmitt]

After further testing, still seeing some strangeness. URL segments in blue are consumers and segments in red contain the cluster name. Periodically seeing 404 response codes from the API when the segments are swapped.

[Kav91]

Yep that is strange, so something is up the new lookup. It's designed to support as many lookups possible now, but it means there is a situation where it can potentially not slot into the correct index.
I'll try and replicate the issue to figure it out.

[Kav91]

@bpschmitt I managed to replicate the issue although intermittently.
Since putting in a fix in 0.9.2, I'm yet to get the issue . Could you please give that release a go?
Hard to 100% confirm its all good from the test data.

[bpschmitt]

I've had this running for a while and everything looks good. Marking as closed. Thanks again!