fix: Use event timestamp based on utcoffset #314
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
celery-exporter has this feature to purge ofline worker metrics which default to 10 minutes. So any worker that is offline for more than 10 minutes, the metrics of which will be purged
Now if celery workers is configured to use PST timezone (which is 7 hours behind UTC) or any other timezone that is not UTC, in such cases celery-exporter (running in UTC tz) considered live workers also to be offline because of this offset and this causes a continuous loop of live worker metrics to be purged and so we get inconsistent metrics.
Temp solution is to set
CE_WORKER_TIMEOUT
andCE_PURGE_OFFLINE_WORKER_METRICS
to 7hrs + 10mins ahead