Advisors require regular review

Impact on the user
Confusion, or loss of confidence.

Steps to reproduce
This is an example of one with an issue:

• deploy a MongoDB 4.2 instance

• monitor via PMM

• run mongodb_EOL advisor

Actual result

• result = "MongoDB version 4.2 is about to reach EOL"

• details = "MongoDB version 4.2 End-of-Life date is 30-Apr-2023. PSMDB and MongoDB follow similar EOL timelines. Please review the software lifecycle policy at the Read More link in the details section and plan your upgrade accordingly. It is recommended to upgrade to the most recent version of your major release for security and performance reasons. "

• severity = warning

Expected Result
Something like:

• result = "MongoDB version 4.2 has reached its EOL"

• details = "MongoDB version 4.2 End-of-Life date was 30-Apr-2023. PSMDB and MongoDB follow similar EOL timelines. Please review the software lifecycle policy at the Read More link in the details section and plan your upgrade accordingly. It is recommended to upgrade to the most recent version of your major release for security and performance reasons. "

• severity = critical

Workaround
N/A

Details
The example detailed here is one specific advisor, however it reveals that the advisors should get a regular review to ensure that information is accurate. The code that generates the advisors can also help here, by simply adding logic around date-based checks.