Your developer tooling and operations are a product, which means that you should treat it like one. When you launch products externally, you add metrics and logging - right? You should be doing the same thing with your developer tooling. Here are a few quick guidelines on what to track and what not to track.

Do Track

These are good examples of things to track

• Time to first boot (how long it takes to start)
• Time to first request (how long it takes to render the first action after booting)
• Time per action
• Failures and exceptions (and who experienced them)
• Number of times actions are hit

Don’t Track

These are good examples of things not to track

• Generally, anything outside of your codebase/things you explicitly control, except in the case where the data is explicit, is scoped, is temporary, and can be used to help guide a project (e.g. how long do git pulls take?)
• Personally identifying information outside failures and exceptions (you need to be able to debug and help a user, but this is still a personal workspace)

TODO THE WHYs FOR EACH Do/Dont