Reduce amount of anonymous analytics events

[pkosiec]

Description

Changes proposed in this pull request:

• Reduce amount of anonymous analytics events

Testing

The easiest way is to reduce the tickDuration in code (Segment Reporter):

 // NewSegmentReporter creates a new SegmentReporter instance.
 func NewSegmentReporter(log logrus.FieldLogger, cli segment.Client) *SegmentReporter {
 	return &SegmentReporter{
 		log:          log,
 		cli:          cli,
 		batchedData:  batched.NewData(defaultTimeWindowInHours),
-		tickDuration: defaultTimeWindowInHours * time.Hour,
+		tickDuration: 10 * time.Seconds,
 	}
 }

In the same file, you can set fixed APIKey:

 var (
 	// APIKey contains the API key for external analytics service. It is set during application build.
-	APIKey string
+	APIKey string = "abc..."
 )

Run Botkube with debug log (export BOTKUBE_SETTINGS_LOG_LEVEL=debug) and observe Segment events in debugger. Emit some sample events.

Screenshots

Related issue(s)

[mszostok]

I didn't test that with real segment, but code LGTM 👍

But please double-check with Ole that Segment.io doesn't have any message size limit.

Because we may switch the events quota problems to size quota problem 😄

If so, we can keep details maybe about N last source events? while counters will still tell about the exact number. This will prevent us from failing to send an event when e.g. agent cluster is misconfigured and someone watches e.g. for all events.

[pkosiec]

Merging as the integration test issue for Discord wasn't related to the PR and Slack tests passed 👍