feat(outputs.azure_data_explorer): Add AppName in connector details

[asaharn]

Summary

Adding App name will help to identify the source plugin of incoming telemetry data eg. Kusto or Microsoft Fabric (upcoming plugin by Microsoft).

Checklist

• No AI generated code was used in this PR

Related issues

resolves #16101

[srebhan]

@asaharn it seems to me as if the AppName is a new setting for the config. If so, you must also add a toml tag and adapt the sample.conf to document the new setting...

[asaharn]

Hi @srebhan, the AppName is restricted to be only accessible internally at telegraf plugin level. This will help us in monitoring the usage telemetry, to differentiate between usage of ADX output plugin. 1) Native Output plugin i.e. "Kusto.Telegraf" or 2) Microsoft Fabric output plugin, i.e. "Fabric.Telegraf" (an upcoming output plugin)

Please note that we will raise the PR for MS Fabric right after this PR gets merged as the changes are ready.

[asaharn]

Hello @srebhan , a gentle ping. Please let us know if there are any required changes.

We have another feature that is blocked due to this PR.

[srebhan]

Sorry but this does not make sense. Why do you add an exported field to a struct that should be used solely internally? Why not just using the string a the SINGLE usage point then?

[asaharn]

Hi @srebhan,
Apologies. But can you take a look here at line 106 of our upcoming internal PR, the reason we came up with this approach. And totally open for better suggestions.

[asaharn]

Hi @srebhan . I think I was able to explain my point. And we welcome suggestions regarding this.

[srebhan]

@asaharn I see your point in the code you linked. Please note you cannot import a plugin in another plugin! That's something we don't want as it is impossible to maintain. Therefore, the correct move would be to move the code common to both plugins into plugins/common/<whatever> and then it makes sense to expose the AppName in that common structure.

Does that make sense?

[telegraf-tiger]

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 change the Telegraf binary size

📦 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

[srebhan]

@asaharn any comment on moving the common part to plugins/common?

[asaharn]

Hi @srebhan, thank you for the suggestion. yes, we are looking for the feasibility to move code for both the connectors to plugins/common.