Quentin Manfroi

hello @keitwb thanks for your fast answer as usual. I am open to contribute of course, I just would like to know if you think it makes sens or not....

> Yes, it absolutely makes sense. I would make a new monitor `mysql` though and not mess with `collectd/mysql` since it would have nothing to do with collectd. I understand...

or I can try to create a new fresh mysql monitor which will wrap `sql` one AND `collectd/mysql` (temporary).

hello @keitwb again a totally understand your point of view but I still would prefer to be able to configure only one monitor with basic conf and retrieve everything we...

@keitwb I spoke to my colleagues and configuring 2 different monitors waiting for the new `mysql` monitor will cover every useful metrics from `collectd/mysql` seem acceptable for them. So I...

browsing the codebase it seems the agent is already able to catch collectd events: https://github.com/signalfx/signalfx-agent/blob/master/pkg/monitors/collectd/collectd.go#L416 I am not sure if we can and how to send custom events from scripts...

sadly it does not seem to provide a builtin function for events: https://github.com/signalfx/signalfx-agent/blob/master/python/sfxmonitor/output.py#L11

thanks @mcmiv413 for your prompt answer. should I understand that any "string" data type from telegraf is handled as events to signalfx ?

@mcmiv413 ok so what I understand is you call the api from your custom script which is the hacky way I mentioned in the issue description. I keep this in...

@mcmiv413 sadly it is a specific script we created for a customer so I cannot share the code here. in many ways it is similar to the official http_check: https://github.com/DataDog/integrations-core/blob/master/http_check/datadog_checks/http_check/http_check.py...