Add a "refresh service" button to the edit service view

54 votes

Some services, like the interface, depend on their previous state.

In order for the new state to be applied the service must be moved to undecided and then moved back to the monitored services.

It would be nice to have an single "refresh service" button in the service edit view that does the same for the selected services in one step.

Implemented Setup Suggested by: Lars Sörensen (06 May, '22) • Upvoted: 20 Oct, '24 • Comments: 14

Comments: 14

26 Apr, '22
Thomas Lippert Admin Merged
Due to a service change, I need to remove a service from a list of Linux servers and rediscover the new service. Unfortunately, this is a host by host operation and not possible via a bulk operation
06 May, '22
Robin Gierse Merged
This is also true for other types of hosts like network equipment.
11 May, '22
Robert Sander Merged
There is bulk discovery.
02 Jun, '22
Robert Sander
Basically a "Tabula Rasa" for a selection of service checks.
13 Jun, '22
Doc
It would be nice to search for one or more service names (regex, tags, labels) and then hit the tabula rasa button over many hosts (regex, tags, labels).
But... the problem here would be that in that second the service could be in the unwanted state again. And then everything starts all over again.
And that brings us back to an API call. Or you can set the desired, default state directly by rule.
29 Jun, '22
Lars Sörensen Merged
The bulk discovery can't refresh individual services. It only overs a Tabula rasa which removes services you mybe want to keep like not running processes.

This would be the same Feature Request like the following, only for Bulk discovery:
https://features.checkmk.com/suggestions/297961/add-a-refresh-service-button-to-the-edit-service-view
22 Jul, '22
Lars Sörensen
The same for periodic service discovery rules:
https://features.checkmk.com/suggestions/312331/wato-periodic-service-discovery-rule-automatically-refresh-services
01 Aug, '22
Thomas Lippert Admin
"Remove and rediscover services on Linux machines in a bulk operation" (suggested by Thomas Lippert on 2022-04-26), including upvotes (10) and comments (3), was merged into this suggestion.
25 Oct, '23
JPT Merged
Maybe there is an option to have the following Feature:

Scenario:
At the initial discovery of a switch the port 7 is DOWN so the OK-State is down and the CRIT-State is up.
Then the Port is beeing used and changes the operational state to UP and goes to CRIT.

What i want to have is an option where i can set the OK-State is now UP without doing a rediscover or an explicit Rule (change state to up or something), e.g a "tabula-rasa light" for only marked services.

JPT
27 Oct, '23
Mohamed Saleh Admin
"DOWN is the new UP" (suggested by JPT on 2023-10-25), including upvotes (1) and comments (0), was merged into this suggestion.
24 May, '24
Martin Hirschvogel Admin
Hello,

Good news: We have started the development process.

So what’s next? Depending on the scope of your idea, this process may include various steps such as detailed requirements research or a specification phase before it is passed on to development. During this process we may contact you for further information.

Warm regards,
Your Checkmk team
1
28 May, '24
Max Voit Merged
Certain services have properties which are detected during discovery but may change and then change to warn/crit. Resetting the property is currently done by disabling and then rediscovering the service, so that the new stats/property value becomes the default.

For example,
- a network interface may change speed (not necessarily due to hardware changes at the host itself)
- mount options may change
- smart stats (e.g. reallocated sectors) may increase

To ease the process "accept new value as default" a specific menu entry or other GUI addition would be welcome. Ideally, that entry might only show up for warn/crit services that actually have values stored on discovery
31 May, '24
Martin Hirschvogel Admin
"Make service rediscovery for resetting service stats/properties easier" (suggested by <Hidden> on 2024-05-28), including upvotes (1) and comments (0), was merged into this suggestion.
06 Dec, '24
Martin Hirschvogel Admin
Hello,

Good news! Your idea has been implemented into our software. The functionality is available upstream and will be published with Checkmk 2.4.

Warm regards,

Your Checkmk team
1