Quirks in telegraf cloud agent Web UI

[aep-sunlife]

I can send test metrics to telegraf when using configuration generated by telegraf config, with the UDP socket enabled, and the default InfluxDB line protocol applied. However, when I send the same metric to telegraf using the cloud Web UI agent configuration generator, then it messes up parsing and interprets the timestamps as zero AKA 1970-0-01.

2025-04-03T15:41:20Z E! [outputs.influxdb_v2] When writing to [https://us-east-1-1.aws.cloud2.influxdata.com/api/v2/write]: failed to write metric to slus-telemetry (will be dropped: 400 Bad Request): invalid: no data written, errors encountered on line(s): line 1: observed timestamp 1970-01-01T00:00:01.743694872+00:00 is outside of the retention period for the namespace: minimum acceptable timestamp is 2025-03-04T15:41:20.901431287+00:00 - line[1374389601248]
2025-04-03T15:41:20Z E! [agent] Error writing to outputs.influxdb_v2: failed to write metric to slus-telemetry (will be dropped: 400 Bad Request): invalid: no data written, errors encountered on line(s): line 1: observed timestamp 1970-01-01T00:00:01.743694872+00:00 is outside of the retention period for the namespace: minimum acceptable timestamp is 2025-03-04T15:41:20.901431287+00:00 - line[1374389601248]

Getting a generic error message for a newly configured cloud agent: Error Listening for Data. Then it links to documentation for local CLI use.

The Web UI appears to provide no option to edit agent configurations.

[aep-sunlife]

Update

Curious if the cloud generated telegraf agent configuration applies a different epoch precision than the locally generated telegraf default configuration file. That could explain why second precision epochs are coming across as zero values.

[Anaisdg]

The Web UI says it uses the default agent settings. Do you know if it’s different than the default generated by telegraf config ?

The Web UI appears to provide no option to edit agent configurations.

You can edit them by clicking the name of the config. I think we could have made it easier to know that you could edit by also adding an explicit “edit” option to the context menu.

You can probably use this to compare the 2 config files if you want to know if there’s a difference between the one they got with the Web UI and the one they got with telegraf config.

Taking a look at the precision section of one one of the configs I generated with the UI, it appears the precision field is left blank, this might be different with the one gotten from telegraf config.