User story #8069
closedBetter tracking of last seen state
Description
One thing that is sometimes really annoying is that in the nodes list, you'll see "Last seen: Never" for nodes that have gone MIA.
I understand this is due to all their reports having been expired.
It would still be a lot, lot, lot better if Rudder let you discern nodes that never sent a report and ones that didn't send one for the last N days.
IMO the last seen date should not be dropped from the database at all.
For better understanding, the difference is in what happens for those states:
A node that didn't send a report in a month is probably off, quick check and delete.
A node that didn't EVER send a report is one that needs investigation and fixing.
It's risky to have those two overlap.
Beside that, it is worrysome when a gui tool reports something that is WRONG.
It can break the trust between user and tool. That is a problem better to avoid.
Updated by Nicolas CHARLES over 8 years ago
- Category changed from Web - UI & UX to Web - Compliance & node report
- Priority changed from N/A to 2
- Target version set to 4.0.0~rc2
I totally agree with you. Displaying wrong info is plainly wrong, plus this change is clearly in line with what we want to do
Updated by François ARMAND about 8 years ago
- Translation missing: en.field_tag_list set to Ease of use
Updated by François ARMAND about 8 years ago
- Target version changed from 4.0.0~rc2 to 4.1.0~beta1
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 4.1.0~beta1 to 4.1.0~beta2
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 4.1.0~beta2 to 4.1.0~beta3
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 4.1.0~beta3 to 4.1.0~rc1
Updated by François ARMAND almost 8 years ago
- Target version changed from 4.1.0~rc1 to 4.2.0~beta1
Updated by Alexis Mousset over 7 years ago
- Target version changed from 4.2.0~beta1 to 4.2.0~beta2
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.2.0~beta2 to 4.2.0~beta3
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.2.0~beta3 to 4.2.0~rc1
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.2.0~rc1 to 4.2.0~rc2
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.2.0~rc2 to 4.2.0
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.0 to 4.2.1
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.1 to 4.2.2
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.2 to 4.2.3
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.3 to 4.2.4
Updated by Benoît PECCATTE almost 7 years ago
- Target version changed from 4.2.4 to Ideas (not version specific)
Updated by Nicolas CHARLES almost 5 years ago
- Target version changed from Ideas (not version specific) to 6.0.5
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES almost 5 years ago
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2831
Updated by Nicolas CHARLES almost 5 years ago
- Related to Enhancement #16941: delete entries from nodes_info when a node is deleted added
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from In progress to Pending technical review
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|9b826b5ae15736338470d7afd07c7bd5181af021.
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.5 which was released today.