Should we remove the reporter aspect of the CATs config?

[ctlong]

Context

The reporter_config key in the CATs config allows a honeycomb reporter to be registered.

The reporter is registered with ginkgo here:

cf-acceptance-tests/cats_suite_test.go

Lines 144 to 164 in 8d1fa91

	reporterConfig := Config.GetReporterConfig()
	if reporterConfig.HoneyCombDataset != "" && reporterConfig.HoneyCombWriteKey != "" {
	honeyCombClient := client.New(libhoney.Config{
	WriteKey: reporterConfig.HoneyCombWriteKey,
	Dataset: reporterConfig.HoneyCombDataset,
	})
	globalTags := map[string]interface{}{
	"run_id": os.Getenv("RUN_ID"),
	"env_api": Config.GetApiEndpoint(),
	}
	honeyCombReporter := honeycomb.New(honeyCombClient)
	honeyCombReporter.SetGlobalTags(globalTags)
	honeyCombReporter.SetCustomTags(reporterConfig.CustomTags)
	rs = append(rs, honeyCombReporter)
	}
	RunSpecsWithDefaultAndCustomReporters(t, "CATS", rs)

We don't reference the reporter config anywhere in the README.

Questions

• Was this included specifically for past maintainers or was the community at large interested in reporting to honeycomb?
• Does anyone register a honeycomb key in their CATs runs and/or look at the results in a honeycomb dashboard?
• Is it worth removing this thing?

[ameowlia]

Was this included specifically for past maintainers or was the community at large interested in reporting to honeycomb?

I think there was a particular pivot who led this initiative. They are no longer working on Cloud Foundry. I do not think there was any community involvement.

Does anyone register a honeycomb key in their CATs runs and/or look at the results in a honeycomb dashboard?

AFAIK we haven't used honeycomb in years.

Is it worth removing this thing?

Yes.