Enhancement #23936
closed
We should log an error when a hook timeouts
Added by Elaad FURREEDAN 11 months ago.
Updated 10 months ago.
Suggestion strength:
Advise - This would make Rudder significantly better | easier | simpler
User visibility:
Infrequent - complex configurations | third party integrations
Fix check:
Error - Next version
Description
It's hard to identify when a hook timeout, there are no obvious clues, it happens a few time that on other users, and it's hard to identify that the problem came from a hook timeout.
I think we should try to improve the detection of error, maybe logging when the hooks timeout may be a good idea (but I don't know the complexity to do this)
It's in the category "server component".
Which hooks are you talking about ? Campaign hooks, server hooks, inventory hooks ?
- Category changed from Server components to Agent
At least the inventories hook,which are often the more likely to fail
another ticket should be done for system update hooks (but i think it's already taken into account there)
- Assignee set to Benoît PECCATTE
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2849
- Status changed from Pending technical review to Pending release
- Subject changed from We should log an error when a hook timeout to We should log an error when a hook timeouts
- Fix check changed from To do to Error - Next version
- Fix check changed from Error - Next version to Error - Blocking
- Fix check changed from Error - Blocking to Error - Next version
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.11 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by