Currently the prober-goroutines are spammend and afterwards the HTTP-endpoint is started. this is nice and easy as it is quite sequential, however, it has the disadvantage that with a restart the exporter is scraped as "down" until all the prober-goroutines have started.
Starting the HTTP-endpoint earlier and after starting the probers hooking into it to not exit would be one way of solving this, starting a "prober-spammer"-coroutine would be the other, probably simpler one.
el-if
commented
7 years ago
Currently the prober-goroutines are spammend and afterwards the HTTP-endpoint is started. this is nice and easy as it is quite sequential, however, it has the disadvantage that with a restart the exporter is scraped as "down" until all the prober-goroutines have started.
Starting the HTTP-endpoint earlier and after starting the probers hooking into it to not exit would be one way of solving this, starting a "prober-spammer"-coroutine would be the other, probably simpler one.