[EPIC] defogging connector health metrics noise

[sherifnada]

Tell us about the problem you're trying to solve

• [EPIC] Ensure Source and Destination errors are distinguished and useful (Defogging phase 0) #12118
• [EPIC] Preventing connector false-positives due to user-error (Defogging phase 1) #12119
• https://github.com/airbytehq/airbyte-cloud/issues/1506

Describe the solution you’d like

Describe the alternative you’ve considered or used

Additional context

[evantahler]

I propose this epic (and child stories) be closed as well

• In the new metrics poposals by @bleonard, we do not need to know if a connection has been disabled or not.
• Incident management is already it's own epic
• Other work roughly captured by [EPIC] Ensure Source and Destination errors are distinguished and useful (Defogging phase 0) #12118 and [EPIC] Preventing connector false-positives due to user-error (Defogging phase 1) #12119

[sherifnada]

@evantahler can you link to the new metrics proposals? i don't believe I've seen them

[bleonard]

@evantahler can you link to the new metrics proposals? i don't believe I've seen them

Near term roadmap of this document.

[sherifnada]

@evantahler I'd like to keep this issue if only as an aggregator of all these other EPICs. It's useful to have a single entry point which encompasses all the things which, when done, constitute a defogged style of life