fix(deps): update module github.com/twmb/franz-go to v1.20.2 (#24)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

[INTERNAL] Log scrape timing

OAUTH support for AdobeIMS (#15)

Co-authored-by: amuraru <[email protected]>

Upgrade deps

Added arm64 build support (#11)

Collect metrics for a set of CG states ADDENDUM (#8)

Collect metrics for a set of CG states (#7)

* Filter empty consumer groups

* Collect metrics for a set of CG states

* Update minion/config_consumer_group.go

Co-authored-by: Adrian Muraru <[email protected]>

* Implement review

* Implement review

* Update the CG state values

---------

Co-authored-by: Adrian Muraru <[email protected]>

Run as non-root and root group for OpenShift compatibility ADDENDUM (#5)

Run as non-root and root group for OpenShift compatibility

See https://developers.redhat.com/blog/2020/10/26/adapting-docker-and-kubernetes-containers-to-run-on-red-hat-openshift-container-platform#group_ownership_and_file_permission

Expose max timestamp for each topic and/or partition (#3)

* Expose max timestamp for each topic and/or partition


Kafka 3.0+ added support to fetch offset with the max timestamp.
This is useful in monitoring the steady progress of producing to a topic/partion
but also to detect very high timestamps in the topic that can stuck topic retention.

This patch adds two new metrics:
- kafka_topic_partition_max_timestamp: for each topic partition reports the max timestamp in that partition
- kafka_topic_max_timestamp: for each topic reports the max timestamp in that topic, computed as the maximum timestamp across partitions


See: 
- https://issues.apache.org/jira/browse/KAFKA-12541
- https://cwiki.apache.org/confluence/display/KAFKA/KIP-734%3A+Improve+AdminClient.listOffsets+to+return+timestamp+and+offset+for+the+record+with+the+largest+timestamp

* Update prometheus/collect_topic_partition_offsets.go