chore: include support metrics in the project

[Ismael Juma (ijuma)]

Description

ksqlDB is the only user of these classes, so include it in the project instead of consuming it as a library.

Source files were copied from Confluent Kafka's support-metrics-common module. They were updated to match ksqlDB checkstyle and to remove functionality that submits metrics to a Kafka topic (this was never used by ksqlDB).

Testing done

Tested by building a docker image and running it locally using the docker-compose file in the ksqldb.io quickstart as a template. Based on inspecting network traffic sent at server startup, there was an HTTP POST to the version-checker endpoint with the expected Avro payload.

POST /ksql/anon HTTP/1.1
api-version: phone-home-v1
Content-Length: 1155
Content-Type: multipart/form-data; boundary=Hf24SYtnRPyDwcgTVg30h6rdXnQ0-Xfw0jC
Host: version-check.confluent.io
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_212)
Accept-Encoding: gzip,deflate

--Hf24SYtnRPyDwcgTVg30h6rdXnQ0-Xfw0jC
Content-Disposition: form-data; name="cid"

anonymous
--Hf24SYtnRPyDwcgTVg30h6rdXnQ0-Xfw0jC
Content-Disposition: form-data; name="file"; filename="filename"
Content-Type: application/octet-stream

Objavro.schema¤{"type":"record","name":"KsqlVersionMetrics","namespace":"io.confluent.ksql.version.metrics","doc":"Represents basic metrics captured on a single ksql component","fields":[{"name":"timestamp","type":"long","doc":"Time when this data record was created on the ksql component (Unix time)."},{"name":"confluentPlatformVersion","type":["null",{"type":"string","avro.java.string":"String"}],"doc":"The version of the Confluent Platform this ksql component is running."},{"name":"ksqlComponentType","type":{"type":"string","avro.java.string":"String"},"doc":"Identifies the ksql component"},{"name":"isActive","type":"boolean","doc":"Indicates if the server was active in the last 24 hours. A server is considered active if it received a rest request or it has at least one running query."}]}ðp�ÛúÜ6&¡·ùÂ:ô¼å�5.5.0-SNAPSHOTSERVERðp�ÛúÜ6&¡·ùÂ
--Hf24SYtnRPyDwcgTVg30h6rdXnQ0-Xfw0jC--

(The ksqldb-server container was configured to send data to the insecure version-checker endpoint, so that the payload could be more easily verified)

Reviewer checklist

• Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
• Ensure relevant issues are linked (description should include text like "Fixes #")

[Colin Hicks (colinhicks)]

I will be helping bring this home. Some follow-ups:

• Ensure Avro-supporting bits from support metrics are copied
• We can remove the configurations for the support metrics topic in BaseSupportConfig, as these were only relevant to Confluent Server.
• Some tests refer to the support-metrics.confluent.io endpoint, which also applied only to Confluent Server. ksqlDB uses version-checker.confluent.io.

[Ismael Juma (ijuma)]

Thank you Colin Hicks (@colinhicks)! A couple of tests that can also be removed:

• proactiveSupportConfigIsValidKafkaConfig
• canParseProactiveSupportConfiguration

[Ismael Juma (ijuma)]

License should be updated to match ksqldb's template.

[Colin Hicks (colinhicks)]

Apurva Mehta (@apurvam), I should rebase this onto 5.5.x, correct?

[Colin Hicks (colinhicks)]

Verified metrics send as expected. See description for testing notes.

[Almog Gavra (agavra)]

Given this is a copy of existing code I didn't give it a thorough review, just a quick scan to see that it does what it claims to 😝

[Ismael Juma (ijuma)]

Colin Hicks (@colinhicks) When merging this, please set yourself as the author since you did all the work. :)

[Colin Hicks (colinhicks)]

Ismael Juma (@ijuma), I could not convince GitHub to make the squash-merge commit in my name, even after rewriting the author name in the initial commit.

If it's best to alter a80a7d8 with my name, we'll need to ask Almog Gavra (@agavra) or another maintainer to amend it – I don't have code-owner rights to this repo.

[Colin Hicks (colinhicks)]

Not sure if GH's behavior has changed here. Noting for myself in the future: squash merging PRs with a different author than the PR creator seems to require manually merging with git.

[Ismael Juma (ijuma)]

I see. One way to make this sort of work is to use co-authored-by to assign multiple authors.