feat(inputs.whois): Add plugin #16509

paulojmdias · 2025-02-12T14:05:27Z

Summary

This PR adds the WHOIS input plugin to Telegraf, allowing users to collect WHOIS data for configured domains. It retrieves expiration timestamps, registrar details, and domain status. The implementation leverages likexian/whois and likexian/whois-parser for efficient lookups and parsing. Tests and documentation are included.

Checklist

No AI generated code was used in this PR

Related issues

resolves #7893

Signed-off-by: Paulo Dias <[email protected]>

Hipska

Thanks for this useful addition.

plugins/inputs/whois/sample.conf

plugins/inputs/whois/README.md

plugins/inputs/whois/whois.go

plugins/inputs/whois/whois_test.go

plugins/inputs/whois/whois.go

Signed-off-by: Paulo Dias <[email protected]>

Signed-off-by: Paulo Dias <[email protected]> Remove file Signed-off-by: Paulo Dias <[email protected]>

…put_whois Signed-off-by: Paulo Dias <[email protected]>

Hipska

Great work, some more comments..

plugins/inputs/whois/whois.go

plugins/inputs/whois/sample.conf

plugins/inputs/whois/README.md

plugins/inputs/whois/whois_test.go

Signed-off-by: Paulo Dias <[email protected]>

plugins/inputs/whois/whois.go

plugins/inputs/whois/whois_test.go

Hipska · 2025-02-13T15:57:06Z

plugins/inputs/whois/whois_test.go

+	plugin.whoisLookup = func(_ *whois.Client, _ string, _ string) (string, error) {
+		return "", errors.New("whois lookup failed")
+	}


Should the lookup fail in this scenario? Or just return an empty result? (No domain info found for %s)

https://github.com/influxdata/telegraf/pull/16509/files#diff-966e99448e0e916462689167835d5a5951da25c52462fd49ecd731516431a5a6R46-R50

To align with the behavior in Gather, I think the lookup should fail, right? WDYT?

I don't know, what happens in real life when doing this to a real WHOIS server?

In what scenario does it return an empty Domain object?

At least on the library, if the lookup fails, the library will throw an error.

The Domain will return an empty object when whoisparser.Parse fails.

But then the returned err will not be null, so the code will never reach that scenario?

It seems I was mislead by the error message "No domain info found for %s", so I start to think the plugin should return a metric with status_code 0 when the whoisLookup fails..

Wait, forget what I said. After looking into the whois parser code. It looks like additional processing of the returned error type needs to be done.

So no metric on whoisLookup error, but metric on all types of whoisParse errors except for ErrDomainDataInvalid and maybe ErrDomainLimitExceed depending on how you see it..

I added the support for additional status_code when an error on failed parsing occurs.

I only ignored ErrDomainDataInvalid since I feel useful to keep ErrDomainLimitExceed for the users to adjust the interval config if needed.

Looks good, still not sure about ErrDomainLimitExceed. IMHO it should be an error message in the log and not report a metric, since it is not a state of the domain. The user will see it has no data for this specific metric, may check the logs and then adjust config.

TLDR; I don't think status code 10 is needed.

I have mixed feelings about that, but I pushed the changes for it. Will throw an error message if the parsing error is ErrDomainDataInvalid or ErrDomainLimitExceed

We can see what the maintainers think of it..

Signed-off-by: Paulo Dias <[email protected]>

Hipska

Looks like we're almost there..

plugins/inputs/whois/whois.go

Hipska · 2025-02-13T16:32:29Z

plugins/inputs/whois/whois_test.go

+	plugin.whoisLookup = func(_ *whois.Client, _ string, _ string) (string, error) {
+		return "", errors.New("whois lookup failed")
+	}


I don't know, what happens in real life when doing this to a real WHOIS server?

In what scenario does it return an empty Domain object?

Hipska · 2025-02-13T16:34:05Z

plugins/inputs/whois/whois.go

+		updated := parsedWhois.Domain.UpdatedDateInTime
+		if updated == nil {
+			w.Log.Warnf("No updated date found for %s", domain)
+			continue


Note that now they will be emitted as field with value 0 (meaning January 1, 1970)

Signed-off-by: Paulo Dias <[email protected]>

Hipska

Great progress!

plugins/inputs/whois/whois.go

plugins/inputs/whois/whois_test.go

Signed-off-by: Paulo Dias <[email protected]>

Hipska

Thanks for being patient! Good work.

paulojmdias · 2025-02-14T15:11:43Z

Thanks for being patient! Good work.

Thanks for helping making this perfect 🙌

srebhan

Thanks for contributing this nice plugin @paulojmdias! I do have some comments in the code. One general thing I would love to see is to mock a WHOIS server in the tests so we can get rid of the function injection. I think the whois lib's unit-test might give a good starting point...

plugins/inputs/whois/README.md

plugins/inputs/whois/whois.go

srebhan · 2025-02-17T10:35:25Z

plugins/inputs/whois/whois.go

+	if w.whoisLookup == nil {
+		w.whoisLookup = func(client *whois.Client, domain, server string) (string, error) {
+			return client.Whois(domain, server)
+		}
+	}
+	if w.parseWhoisData == nil {
+		w.parseWhoisData = func(raw string) (whoisparser.WhoisInfo, error) {
+			return whoisparser.Parse(raw)
+		}
+	}


I would really appreciate if we can get rid of this indirection that is solely there for testing. Can we rather mock a WHOIS server response in the tests? In any case this could be

Suggested change

if w.whoisLookup == nil {

w.whoisLookup = func(client *whois.Client, domain, server string) (string, error) {

return client.Whois(domain, server)

}

}

if w.parseWhoisData == nil {

w.parseWhoisData = func(raw string) (whoisparser.WhoisInfo, error) {

return whoisparser.Parse(raw)

}

}

if w.whoisLookup == nil {

w.whoisLookup = func(client *whois.Client, domain, server string) (string, error) {

return client.Whois(domain, server)

}

}

if w.parseWhoisData == nil {

w.parseWhoisData = whoisparser.Parse

}

I removed the code function overwrite in the tests also. Please double-check for now.

However, you want to have some tests like this for this plugin? With some custom files on this side?

Exactly. We do have some tests (e.g. here) with some "test cases" being a self-contained directly each and some testing mock to send the test-case data to the plugin...

plugins/inputs/whois/sample.conf

plugins/inputs/whois/whois.go

srebhan · 2025-02-17T10:59:26Z

plugins/inputs/whois/whois_test.go

+	// Validate `expiration_timestamp` field (2025-08-13T04:00:00Z → Unix)
+	expectedExpiration := int64(1755057600)
+	expirationValue, found := acc.Int64Field("whois", "expiration_timestamp")
+	require.True(t, found, "expiration_timestamp field missing")
+	require.InDelta(t, expectedExpiration, expirationValue, 10)
+
+	// Validate `expiry` field
+	now := time.Now()
+	expectedExpiry := int(expectedExpiration - now.Unix())
+	expiryValue, found := acc.IntField("whois", "expiry")
+	require.True(t, found, "expiry field missing")
+	require.InDelta(t, expectedExpiry, expiryValue, 10) // Allow small delta due to execution time


This calls for flaky tests as sometimes the CI infrastructure has a really high load and will likely exceed your delta. As you mock the response, how about putting an exact time in there we can check for?

Don't disagree, however, the expiry will always be dynamic, since is computed based on the current timestamp. What did you suggest here?

I don't think makes sense to do something like the below since will also fail in make lint tests. Maybe remove the required value validation from expiry?

require.Equal(t, expiryValue, expiryValue)

You can ignore the fields that are computed in the comparison using the testutil.IgnoreFields option and then afterwards just check it is require.Positive?

@srebhan i pushed using the same approach as x509_cert which uses testutil.IgnoreFields("expiry"). IdK if you want to keep the same approach or not, but please let me know.

@srebhan I only saw your last comment after my push. Please review my changes again 🙏

plugins/inputs/whois/whois_test.go

Co-authored-by: Sven Rebhan <[email protected]>

Signed-off-by: Paulo Dias <[email protected]>

Hipska · 2025-02-17T13:50:06Z

plugins/inputs/whois/whois.go

+		return &Whois{
+			Timeout: config.Duration(5 * time.Second),
+		}


Missing the default value for Server

Thanks for the heads-up. This makes me find the server sent to the Client is not working with the same behavior as being empty. I have different outputs if I send whois.iana.org as a server or if I send nothing to the client.

Output setting server as empty:

whois,domain=influxdata-test.com status_code=6i 1739542332000000000

Output setting server as the supposed default whois.iana.org:

> whois,domain=influxdata-test.com creation_timestamp=473385600i,dnssec_enabled=false,expiration_timestamp=0i,expiry=0i,name_servers="a.gtld-servers.net,b.gtld-servers.net,c.gtld-servers.net,d.gtld-servers.net,e.gtld-servers.net,f.gtld-servers.net,g.gtld-servers.net,h.gtld-servers.net,i.gtld-servers.net,j.gtld-servers.net,k.gtld-servers.net,l.gtld-servers.net,m.gtld-servers.net",registrant="",registrar="",status_code=5i,updated_timestamp=1701907200i 1739809813000000000

Technically, what is happening is (like whois CLI), when we send a server, the whois won't follow redirection if it is not explicitly defined, which leads to only parsing the data from the TLD, which is this case is .com

-Q Do a quick lookup; whois will not attempt to follow referrals to other whois servers. This is the default if a server is explicitly specified using one of the other options or in an environment variable. See also the -R option.

Result with the default behavior:

❯ whois -h whois.iana.org influxdata-test.com % IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.verisign-grs.com domain: COM organisation: VeriSign Global Registry Services address: 12061 Bluemont Way address: Reston VA 20190 address: United States of America (the) contact: administrative name: Registry Customer Service organisation: VeriSign Global Registry Services address: 12061 Bluemont Way address: Reston VA 20190 address: United States of America (the) phone: +1 703 925-6999 fax-no: +1 703 948 3978 e-mail: [email protected] contact: technical name: Registry Customer Service organisation: VeriSign Global Registry Services address: 12061 Bluemont Way address: Reston VA 20190 address: United States of America (the) phone: +1 703 925-6999 fax-no: +1 703 948 3978 e-mail: [email protected] nserver: A.GTLD-SERVERS.NET 192.5.6.30 2001:503:a83e:0:0:0:2:30 nserver: B.GTLD-SERVERS.NET 192.33.14.30 2001:503:231d:0:0:0:2:30 nserver: C.GTLD-SERVERS.NET 192.26.92.30 2001:503:83eb:0:0:0:0:30 nserver: D.GTLD-SERVERS.NET 192.31.80.30 2001:500:856e:0:0:0:0:30 nserver: E.GTLD-SERVERS.NET 192.12.94.30 2001:502:1ca1:0:0:0:0:30 nserver: F.GTLD-SERVERS.NET 192.35.51.30 2001:503:d414:0:0:0:0:30 nserver: G.GTLD-SERVERS.NET 192.42.93.30 2001:503:eea3:0:0:0:0:30 nserver: H.GTLD-SERVERS.NET 192.54.112.30 2001:502:8cc:0:0:0:0:30 nserver: I.GTLD-SERVERS.NET 192.43.172.30 2001:503:39c1:0:0:0:0:30 nserver: J.GTLD-SERVERS.NET 192.48.79.30 2001:502:7094:0:0:0:0:30 nserver: K.GTLD-SERVERS.NET 192.52.178.30 2001:503:d2d:0:0:0:0:30 nserver: L.GTLD-SERVERS.NET 192.41.162.30 2001:500:d937:0:0:0:0:30 nserver: M.GTLD-SERVERS.NET 192.55.83.30 2001:501:b1f9:0:0:0:0:30 ds-rdata: 19718 13 2 8acbb0cd28f41250a80a491389424d341522d946b0da0c0291f2d3d771d7805a whois: whois.verisign-grs.com status: ACTIVE remarks: Registration information: http://www.verisigninc.com created: 1985-01-01 changed: 2023-12-07 source: IANA

Results explicitly saying to follow redirects when the server is set:

❯ whois -h whois.iana.org -R influxdata-test.com % IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.verisign-grs.com domain: COM organisation: VeriSign Global Registry Services address: 12061 Bluemont Way address: Reston VA 20190 address: United States of America (the) contact: administrative name: Registry Customer Service organisation: VeriSign Global Registry Services address: 12061 Bluemont Way address: Reston VA 20190 address: United States of America (the) phone: +1 703 925-6999 fax-no: +1 703 948 3978 e-mail: [email protected] contact: technical name: Registry Customer Service organisation: VeriSign Global Registry Services address: 12061 Bluemont Way address: Reston VA 20190 address: United States of America (the) phone: +1 703 925-6999 fax-no: +1 703 948 3978 e-mail: [email protected] nserver: A.GTLD-SERVERS.NET 192.5.6.30 2001:503:a83e:0:0:0:2:30 nserver: B.GTLD-SERVERS.NET 192.33.14.30 2001:503:231d:0:0:0:2:30 nserver: C.GTLD-SERVERS.NET 192.26.92.30 2001:503:83eb:0:0:0:0:30 nserver: D.GTLD-SERVERS.NET 192.31.80.30 2001:500:856e:0:0:0:0:30 nserver: E.GTLD-SERVERS.NET 192.12.94.30 2001:502:1ca1:0:0:0:0:30 nserver: F.GTLD-SERVERS.NET 192.35.51.30 2001:503:d414:0:0:0:0:30 nserver: G.GTLD-SERVERS.NET 192.42.93.30 2001:503:eea3:0:0:0:0:30 nserver: H.GTLD-SERVERS.NET 192.54.112.30 2001:502:8cc:0:0:0:0:30 nserver: I.GTLD-SERVERS.NET 192.43.172.30 2001:503:39c1:0:0:0:0:30 nserver: J.GTLD-SERVERS.NET 192.48.79.30 2001:502:7094:0:0:0:0:30 nserver: K.GTLD-SERVERS.NET 192.52.178.30 2001:503:d2d:0:0:0:0:30 nserver: L.GTLD-SERVERS.NET 192.41.162.30 2001:500:d937:0:0:0:0:30 nserver: M.GTLD-SERVERS.NET 192.55.83.30 2001:501:b1f9:0:0:0:0:30 ds-rdata: 19718 13 2 8acbb0cd28f41250a80a491389424d341522d946b0da0c0291f2d3d771d7805a whois: whois.verisign-grs.com status: ACTIVE remarks: Registration information: http://www.verisigninc.com created: 1985-01-01 changed: 2023-12-07 source: IANA # whois.verisign-grs.com No match for domain "INFLUXDATA-TEST.COM". >>> Last update of whois database: 2025-02-17T18:34:30Z <<<

So, I do not understand why the library is not respecting the disableReferral, which by default is false, but either way, it seems the return comes from here.

Due to these concerns, does it make sense to support custom whois servers, or should we open an issue and let that happen for the next interaction?

The main issue is on this line. When a server is provided, in the end, they return an answer from all the steps. When is not provided, the library will get the server at this point, query directly the server here and if there is not any additional whois referral server, will return here.

I guess it is best to report that issue upstream, since they are providing a way to set a custom server, it should be supported.

likexian/whois#55

srebhan

Update to my comments...

srebhan · 2025-02-17T15:37:29Z

plugins/inputs/whois/README.md

+⭐ Telegraf v1.34.0
+
+🏷️ network, web
+
+💻 all


Please do not introduce empty lines between those to keep the same format as for other plugins!

Suggested change

⭐ Telegraf v1.34.0

🏷️ network, web

💻 all

⭐ Telegraf v1.34.0

🏷️ network, web

💻 all

This will make appear everything on the same line, shouldn't be more readable to keep it in different lines?

plugins/inputs/whois/whois.go

srebhan · 2025-02-17T15:39:08Z

plugins/inputs/whois/whois.go

+
+	// Ensure timeout is valid
+	if w.Timeout <= 0 {
+		return fmt.Errorf("%v is an invalid timeout value", w.Timeout)


Suggested change

return fmt.Errorf("%v is an invalid timeout value", w.Timeout)

return errors.New("negative timeouts are not supported")

The condition is less or equal 0. So, not only negative timeouts.

Maybe something like negative timeouts or 0 are not supported?

plugins/inputs/whois/whois.go

plugins/inputs/whois/whois_test.go

srebhan · 2025-02-17T15:46:44Z

plugins/inputs/whois/whois_test.go

+	// Validate `expiration_timestamp` field (2025-08-13T04:00:00Z → Unix)
+	expectedExpiration := int64(1755057600)
+	expirationValue, found := acc.Int64Field("whois", "expiration_timestamp")
+	require.True(t, found, "expiration_timestamp field missing")
+	require.InDelta(t, expectedExpiration, expirationValue, 10)
+
+	// Validate `expiry` field
+	now := time.Now()
+	expectedExpiry := int(expectedExpiration - now.Unix())
+	expiryValue, found := acc.IntField("whois", "expiry")
+	require.True(t, found, "expiry field missing")
+	require.InDelta(t, expectedExpiry, expiryValue, 10) // Allow small delta due to execution time


You can ignore the fields that are computed in the comparison using the testutil.IgnoreFields option and then afterwards just check it is require.Positive?

Signed-off-by: Paulo Dias <[email protected]>

telegraf-tiger · 2025-02-18T18:19:51Z

Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip.
Downloads for additional architectures and packages are available below.

☺️ This pull request doesn't significantly change the Telegraf binary size (less than 1%)

📦 Click here to get additional PR build artifacts

Artifact URLs

DEB	RPM	TAR GZ	ZIP
amd64.deb	aarch64.rpm	darwin_amd64.tar.gz	windows_amd64.zip
arm64.deb	armel.rpm	darwin_arm64.tar.gz	windows_arm64.zip
armel.deb	armv6hl.rpm	freebsd_amd64.tar.gz	windows_i386.zip
armhf.deb	i386.rpm	freebsd_armv7.tar.gz
i386.deb	ppc64le.rpm	freebsd_i386.tar.gz
mips.deb	riscv64.rpm	linux_amd64.tar.gz
mipsel.deb	s390x.rpm	linux_arm64.tar.gz
ppc64el.deb	x86_64.rpm	linux_armel.tar.gz
riscv64.deb		linux_armhf.tar.gz
s390x.deb		linux_i386.tar.gz
		linux_mips.tar.gz
		linux_mipsel.tar.gz
		linux_ppc64le.tar.gz
		linux_riscv64.tar.gz
		linux_s390x.tar.gz

feat(inputs.whois): add input plugin for whois data

67e03e4

Signed-off-by: Paulo Dias <[email protected]>

telegraf-tiger bot added feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin plugin/input 1. Request for new input plugins 2. Issues/PRs that are related to input plugins labels Feb 12, 2025

fix: fix readme linting

a04eea9

Signed-off-by: Paulo Dias <[email protected]>

Hipska suggested changes Feb 12, 2025

View reviewed changes

paulojmdias added 2 commits February 13, 2025 12:42

revert changes on this file, not finished with it yet

aaeb51f

Signed-off-by: Paulo Dias <[email protected]>

fix: improvements

daa605b

Signed-off-by: Paulo Dias <[email protected]> Remove file Signed-off-by: Paulo Dias <[email protected]>

paulojmdias force-pushed the input_whois branch from 2289433 to daa605b Compare February 13, 2025 12:50

paulojmdias added 2 commits February 13, 2025 12:54

fix: improvements

4caa207

Signed-off-by: Paulo Dias <[email protected]> Remove file Signed-off-by: Paulo Dias <[email protected]>

Merge branch 'input_whois' of github.com:paulojmdias/telegraf into in…

c0fef67

…put_whois Signed-off-by: Paulo Dias <[email protected]>

Hipska suggested changes Feb 13, 2025

View reviewed changes

paulojmdias added 7 commits February 13, 2025 14:15

fix: improvements

a4ddc91

Signed-off-by: Paulo Dias <[email protected]>

fix: fix testing

9bc3078

Signed-off-by: Paulo Dias <[email protected]>

fix: add registrant

4bdd1aa

Signed-off-by: Paulo Dias <[email protected]>

fix: improvements on variables actions

b28227c

Signed-off-by: Paulo Dias <[email protected]>

fix: unify status_code

4aa3331

Signed-off-by: Paulo Dias <[email protected]>

fix: fix panic on Timestamps when nil

7ebddd1

Signed-off-by: Paulo Dias <[email protected]>

fix: improve docs

27a8079

Signed-off-by: Paulo Dias <[email protected]>

Hipska suggested changes Feb 13, 2025

View reviewed changes

paulojmdias added 2 commits February 13, 2025 16:04

fix: simplify variable assignments

b3ff6a5

Signed-off-by: Paulo Dias <[email protected]>

fix: add timeout test

ce03686

Signed-off-by: Paulo Dias <[email protected]>

Hipska suggested changes Feb 13, 2025

View reviewed changes

paulojmdias added 3 commits February 13, 2025 17:34

fix: remove force init call

c3c0720

Signed-off-by: Paulo Dias <[email protected]>

feat: add support for additional status code in case of failed parsing

00f64c0

Signed-off-by: Paulo Dias <[email protected]>

fix: remove metric when ErrDomainLimitExceed or ErrDomainDataInvalid

dc06f2c

Signed-off-by: Paulo Dias <[email protected]>

Hipska suggested changes Feb 14, 2025

View reviewed changes

fix: simplify functions and tests

e7265bc

Signed-off-by: Paulo Dias <[email protected]>

Hipska approved these changes Feb 14, 2025

View reviewed changes

srebhan reviewed Feb 17, 2025

View reviewed changes

srebhan changed the title ~~feat(inputs.whois): add input plugin for whois data~~ feat(inputs.whois): Add plugin Feb 17, 2025

srebhan self-assigned this Feb 17, 2025

srebhan added the new plugin label Feb 17, 2025

paulojmdias and others added 11 commits February 17, 2025 11:33

Update plugins/inputs/whois/README.md

566a1ed

Co-authored-by: Sven Rebhan <[email protected]>

fix: fix linting and readme

8d87414

Signed-off-by: Paulo Dias <[email protected]>

fix: update registrar and registrant assignment

e05a548

Signed-off-by: Paulo Dias <[email protected]>

chore: update rawWhois and parsedWhois assignment names to raw and data

f7f2417

Signed-off-by: Paulo Dias <[email protected]>

chore: move Debug logs to Trace level

3ecdae9

Signed-off-by: Paulo Dias <[email protected]>

chore: remove log message

a07d1c6

Signed-off-by: Paulo Dias <[email protected]>

fix: return error when timeout is invalid

94a4b68

Signed-off-by: Paulo Dias <[email protected]>

fix: fix docs

d3a6bd9

Signed-off-by: Paulo Dias <[email protected]>

fix: fix timeout tests

573713f

Signed-off-by: Paulo Dias <[email protected]>

fix: remove func override from the tests

1e4af8b

Signed-off-by: Paulo Dias <[email protected]>

chore: update docs

e83026d

Signed-off-by: Paulo Dias <[email protected]>

Hipska suggested changes Feb 17, 2025

View reviewed changes

srebhan reviewed Feb 17, 2025

View reviewed changes

paulojmdias and others added 3 commits February 17, 2025 15:48

fix: update tests and defaults assignments

a4be1b6

Signed-off-by: Paulo Dias <[email protected]>

fix: remove ptr from tests as uneeded

4b78e3e

Signed-off-by: Paulo Dias <[email protected]>

Merge branch 'influxdata:master' into input_whois

4067f6f

paulojmdias mentioned this pull request Feb 18, 2025

chore(linters): Enforce import hrouping with gci linter #16526

Open

1 task

	return fmt.Errorf("%v is an invalid timeout value", w.Timeout)
	return errors.New("negative timeouts are not supported")

feat(inputs.whois): Add plugin #16509

Are you sure you want to change the base?

feat(inputs.whois): Add plugin #16509

Conversation

paulojmdias commented Feb 12, 2025

Summary

Checklist

Related issues

Hipska left a comment

Choose a reason for hiding this comment

Hipska left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Hipska Feb 14, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Hipska Feb 14, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Hipska left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Hipska left a comment

Choose a reason for hiding this comment

Hipska left a comment

Choose a reason for hiding this comment

paulojmdias commented Feb 14, 2025

srebhan left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

paulojmdias Feb 17, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

paulojmdias Feb 17, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

srebhan left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

telegraf-tiger bot commented Feb 18, 2025

Artifact URLs

Hipska Feb 14, 2025 •

edited

Loading

Hipska Feb 14, 2025 •

edited

Loading

paulojmdias Feb 17, 2025 •

edited

Loading

paulojmdias Feb 17, 2025 •

edited

Loading