event-exporter v0.4.1

Increase factor and count of record_latency_seconds.

event-exporter v0.4.0

Improve memory usage of event-exporter.

• event-exporter is a single replica deployment on user nodes. It currently consumes a significant amount of memory for large clusters (e.g., 800MB for 5k node cluster, 3.5 GB for 15k node cluster).
• To improve memory usage, we no longer store any watched events in memory and we only store a limited (1 item) amount of listed events to assist with Watch.
• After the improvement, memory is < 25 MB and does not increase with the number of nodes or events (e.g., 17 MB in 100 node cluster, 19 MB in 5k node cluster, 20 MB in 15k node cluster).
• The improvement does not change CPU usage and logging completeness.

prom-to-sd-v0.11.5

• Fix Go 1.17 to 1.17-alpine to use apk

prom-to-sd-v0.11.4

• Update Go version to 1.17

event-exporter-v0.3.10: Merge pull request #463 from sophieliu15/update_dep_makefile_1

• Upgrade dependencies and go version to 1.17
• Add a metric to measure latency between event creation/update and delivery.

event-exporter v0.3.9

Update Event Exporter log entry timestamp.

If lastTImestamp and lastObservedTime are not set, Event Exporter
will not set log entry timestamp. In this case, Cloud Logging will set
the timestamp to the time when Cloud Logging receives the entry.

event-exporter v0.3.8

Support k8s.io/api/events/v1 API in Event Exporter.

event-exporter v0.3.7

Include fix for calculation of metrics stackdriver_sink_received_entry_count.

event-exporter v0.3.6

Include fix for calculation of metrics stackdriver_sink_successfully_sent_entry_count.

event-exporter v0.3.5

Introduce multi-arch support.