Skip to content

Conversation

@blogh
Copy link
Collaborator

@blogh blogh commented Jan 16, 2026

With this patch Warning is raised when the time since configuration change
is less than the warning threshold. Obviously these alerts will disappear from
themselves once enough time has passed. This doesn't apply for configuration
changes with pending restart warnings.

Eg:

./check_pgactivity -s settings -h /var/run/postgresql -p 5433  -w 1s

Closes #405

The Critical thresholds is ignored.
A Critical is raised if at least one parameter changed.
Warning is raised when the time since configuration change is less than the
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpicking: since configuration change or since the 1st time a change was detected?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the first time this particular change was detected.

@blogh blogh force-pushed the setting_service_timeout branch from 5b555f3 to 02d9afe Compare January 16, 2026 15:59
@blogh
Copy link
Collaborator Author

blogh commented Jan 16, 2026

rebase

@Krysztophe
Copy link
Collaborator

Works for me! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Settings service: timeout to avoid --save

2 participants