stackdriver exporter sometimes loses metric on shutdown

[quentin-cha]

/area monitoring
/kind feature

Expected Behavior

stackdriver exporter do not lose metrics when shutting down

Actual Behavior

stackdriver exporter sometimes lose metrics when shutting down

Additional Info

Currently during process shutdown, stackdriver exporters may lose metrics.
This is happening because:

• Flushing isn't happening correctly, this will soon be fixed.
• Shutdown sequence needs to be: Stop exporter -> Wait for minimum stackdriver upload interval (~10s) -> Flush

[quentin-cha]

/assign

[skonto]

@quentin-cha what is left to be done here? I see that the fix flushes the interval reader so we need to bring the dep in, other than that what is pending the flushing part? @evankanderson Any reason we dont flush the exporter after we replace it here?
Currently we only flush exporters when the process is shutting down.

[quentin-cha]

Apologies for not being able to work on this. Besides pulling in the dep, we need to actually invoke StopMetricsExporter() before we invoke FlushExporter(). The complication is that export to stackdriver is rate limited to once very ~10s so in order to guarantee not losing any metrics, there should be a 10s sleep between StopMetricsExporter() and FlushExporter()

[evankanderson]

I've been chatting with @MontyCarter, and he suggested that we may be able to retire the Stackdriver exporter before 0.22.

I'm assuming this affects OpenCensus as well, though?

[skonto]

It affects opencensus. Should we open an issue for the retirement thing, @MontyCarter gentle ping.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[MontyCarter]

Sorry. Not sure how I missed this. Anyway, the stackdriver exporter can be removed.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[dprotaso]

stack driver exporter was removed