Classic confinement request - telegraf


#1

Hi,

I have created a snap for telegraf (https://github.com/influxdata/telegraf/).
Its purpose is to run a wide variety of input plugins (https://github.com/influxdata/telegraf/blob/master/plugins/inputs/all/all.go), which are chosen by the user in their telegraf.conf file. It is therefore not possible to strictly confine the snap.

Here is the snapcraft file: https://github.com/sajoupa/telegraf/blob/master/snap/snapcraft.yaml

https://dashboard.snapcraft.io/snaps/telegraf-sajoupa/revisions/1/

Thanks,
Laurent


Classic confinement request - telegraf
#2

This is not specific enough to understand why it needs classic. It seems that the plugins are supplied by the snap itself, so the plugins are not arbitrary commands. It also seems that this is about gather metrics, of which we have several interfaces that allow info gathering.

Have you tried strict mode and using snappy-debug to see if it isn’t possible to run in strict mode? Can you provide more specific details on why strict mode is not sufficient?

Also, the snap is called telegraf-sajoupa; what relationship does this snap have with upstream telegraf?


#3

@sajoupa - this request cannot be processed until the requested information is provided. Thanks


#4

Hi,

My main concern is that there are (as of now) 152 different input plugins, 31 outputs.
Users manage which plugins are in use in their config file. And for each plugin, usage will be different depending on that config.
The task of testing these plugins seems enormous, and moreover, might not be enough because activating a particular option in a plugin might require a new interface. And with each telegraf release, new plugins are added.

The name ‘telegraf’ is already reserved apparently. I’m not affiliated with influxdata/telegraf, and would like to have a working published snap before considering to have it pushed with the official name, so I went with telegraf-sajoupa.

Thanks,
Laurent