Port data collection interval issues using flex about nri-flex

[Kav91]

Hi, I think I spoke with another Relic internally today in regards to this issue you were experiencing.

On point number 2, integrations do not execute on the dot of each 30sec interval. It is 30seconds from after the time of completion. So if you had Flex doing a job that takes 15seconds, the next interval is after 15s + 30s. So the behaviour you are seeing is correct and is actually something to do with the infrastructure agent and not Flex itself.

The purpose behind this behaviour is to cater for situations where integrations could potentially take a very long or unexpected time to complete before the next interval starts so we avoid unpredictable queuing behaviours.

The suggestion that was provided was to use the lookup file functionality.
https://github.com/newrelic/nri-flex/wiki/Functions#lookup_file
https://github.com/newrelic/nri-flex/blob/master/examples/flexConfigs/port-test-with-lookup.yml

The lookup file will split each port test you have into a separate config file dynamically.
Flex configs are executed asynchronously meaning that all port tests would fire at once, rather then waiting for each to finish before proceeding to the next.
This way the delay will be at most be the minor execution time + the timeout period given anything does timeout.

Let me know if the above clears up your question, and if the lookup file solution works for you .

[dokyun-kim]

Hello Kav91, Thank you for your answer.

I tried using the lookup type but there was still a delay.
Currently I received a response from another NewRelic engineer to reinstall the infra agent.
Because of the "cannot find configuration" and "unmarshal" errors in the log files of the NewRelic 1.8.14 agent.

I'll check the issue after reinstalling the latest version of NewRelic Infra Agnet.

Thank you!!

[Kav91]

No problem.

If you still have issues with the lookup file option, just share your Flex Config, and the lookup file, so we can best try to replicate and debug it.