Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix gpbackup_backup_since_last_completion_seconds metric. #9

Merged
merged 2 commits into from
May 4, 2024

Conversation

woblerr
Copy link
Owner

@woblerr woblerr commented May 3, 2024

It wasn't taken into account that endtime already contains a timezone. Therefore, the gpbackup_backup_since_last_completion_seconds metric showed incorrect values if the Greenplum cluster works not in UTC timezone.

With a high probability, the exporter will work in the same timezone as Greenplum cluster. Added accounting for the local timezone when parsing the endtime value.

When running exporter in docker, it is necessary to specify correct timezone via TZ variable.

It wasn't taken into account that end time already contains a timezone. With a high probability, the exporter will work in the same timezone as Greenplum cluster. If this isn't the case, then there are many questions about the backup process.
Update the entrypoint in the image to be able to specify  timezone when launching the container.
@woblerr woblerr added the bug Something isn't working label May 3, 2024
@woblerr woblerr self-assigned this May 3, 2024
@woblerr woblerr merged commit 2ecffa7 into master May 4, 2024
6 checks passed
@woblerr woblerr deleted the fix_since_last_completion_metrics branch May 4, 2024 06:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant