Sending Metrics to SumoLogic Stopped Working in v1.27

alx-sg commented 1 year ago

Relevant telegraf.conf

[[outputs.sumologic]]
   url = "https://endpoint1.collection.us2.sumologic.com/receiver/v1/http/[...snip...]"
   data_format = "prometheus"

Logs from Telegraf

systemd[1]: Starting Telegraf...
telegraf[11590]: 2023-06-27T12:28:50Z I! Loading config: /etc/telegraf/telegraf.conf
telegraf[11590]: 2023-06-27T12:28:50Z I! Starting Telegraf 1.27.1
telegraf[11590]: 2023-06-27T12:28:50Z I! Available plugins: 237 inputs, 9 aggregators, 28 processors, 23 parsers, 59 outputs, 4 secret-stores
telegraf[11590]: 2023-06-27T12:28:50Z I! Loaded inputs: cpu disk diskio jolokia2_agent kernel mem processes swap system
telegraf[11590]: 2023-06-27T12:28:50Z I! Loaded aggregators:
telegraf[11590]: 2023-06-27T12:28:50Z I! Loaded processors:
telegraf[11590]: 2023-06-27T12:28:50Z I! Loaded secretstores:
telegraf[11590]: 2023-06-27T12:28:50Z I! Loaded outputs: sumologic
telegraf[11590]: 2023-06-27T12:28:50Z I! Tags enabled: host=hostname123
telegraf[11590]: 2023-06-27T12:28:50Z I! [agent] Config: Interval:1m0s, Quiet:false, Hostname:"hostname123", Flush Interval:10s
telegraf[11590]: 2023-06-27T12:28:50Z E! [agent] Failed to connect to [outputs.sumologic], retrying in 15s, error was "sumologic: incorrect configuration: unsupported serializer *models.RunningSerializer"
systemd[1]: Started Telegraf.
telegraf[11590]: 2023-06-27T12:29:05Z E! [telegraf] Error running agent: connecting output outputs.sumologic: error connecting to output "outputs.sumologic": sumologic: incorrect configuration: unsupported serializer *models.RunningSerializer
systemd[1]: telegraf.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: telegraf.service: Failed with result 'exit-code'.
systemd[1]: telegraf.service: Service RestartSec=100ms expired, scheduling restart.
systemd[1]: telegraf.service: Scheduled restart job, restart counter is at 199.
systemd[1]: Stopped Telegraf.

System info

RHEL8, Telegraf 1.27.x

Docker

n/a

Steps to reproduce

When starting the service, after upgrading from version 1.26 to 1.27

Expected behavior

Service started OK in version 1.26 but stopped working in 1.27.0 and 1.27.1

Actual behavior

The service did not start anymore after upgrade

Additional info

No response

srebhan commented 1 year ago

@alx-sg can you please test the binary in #13522 once CI finished the tests successfully!? Please let me know if this fixes your issue!