Clarify best practice for storing history data: log destinations - Githubissues

fleetdm / fleet

Open-source platform for IT, security, and infrastructure teams. (Linux, macOS, Chrome, Windows, cloud, data center)

https://fleetdm.com

Other

2.94k stars 409 forks source link

Clarify best practice for storing history data: log destinations #22224

Open noahtalerman opened 1 day ago

noahtalerman commented 1 day ago

Goal

User story
As a new Fleet user writing a query,
I want to see copy that explains that log destinations are used for storing historical data while Fleet can be used to see the most recent results
so that I can continue to the next step of connecting Fleet to a log destination if I want to store historical results

Context

Product designer: @rachaelshaw

Original request:

22012

Changes

Product

[ ] Reference documentation changes: TODO
[ ] UI changes: TODO
[ ] CLI (fleetctl) usage changes: TODO
[ ] YAML changes: TODO
[ ] REST API changes: TODO
[ ] Fleet's agent (fleetd) changes: TODO
[ ] Activity changes: TODO
[ ] Permissions changes: TODO
[ ] Changes to paid features or tiers: TODO
[ ] Once shipped, requester has been notified

Engineering

[ ] Feature guide changes: TODO
[ ] Database schema migrations: TODO
[ ] Load testing: TODO

ℹ️ Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

Requires load testing: TODO
Risk level: Low / High TODO
Risk description: TODO

Manual testing steps

Step 1
Step 2
Step 3

Testing notes

Confirmation

[ ] Engineer (@____): Added comment to user story confirming successful completion of QA.
[ ] QA (@____): Added comment to user story confirming successful completion of QA.

noahtalerman commented 1 day ago

Original request:

22012

@rachaelshaw I pulled this new user story off the original request above (also in the issue description). I assigned you and added it to the drafting board.