Skip to content

Conversation

StevenSeeger
Copy link

Description

Link to tracking issue

Fixes #43645

Testing

Testing to ensure that precision was correctly used

Documentation

Pointed to the Influx Docs for OSS Core 3 to help determine which precision to use for which endpoint

@StevenSeeger StevenSeeger requested a review from a team as a code owner October 18, 2025 21:20
@StevenSeeger StevenSeeger requested a review from mwear October 18, 2025 21:20
Copy link

linux-foundation-easycla bot commented Oct 18, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

@github-actions github-actions bot added the first-time contributor PRs made by new contributors label Oct 18, 2025
Copy link
Contributor

Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib.

Important reminders:

A maintainer will review your pull request soon. Thank you for helping make OpenTelemetry better!

@StevenSeeger StevenSeeger changed the title precision fix [exporter/influxdbporter] precision fix Oct 18, 2025
@StevenSeeger StevenSeeger changed the title [exporter/influxdbporter] precision fix [exporter/influxdbporter] FIXES precision Oct 18, 2025
Copy link
Member

@paulojmdias paulojmdias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please add a changelog entry?

@StevenSeeger
Copy link
Author

Can you please add a changelog entry?

Just pushed it - made the PR before checking out the contributing guidelines 🤦

@StevenSeeger StevenSeeger changed the title [exporter/influxdbporter] FIXES precision [exporter/influxdb] FIXES precision Oct 18, 2025
StevenSeeger and others added 2 commits October 18, 2025 17:10
Co-authored-by: Paulo Dias <44772900+paulojmdias@users.noreply.github.com>
Co-authored-by: Paulo Dias <44772900+paulojmdias@users.noreply.github.com>
@paulojmdias
Copy link
Member

/label waiting-for-code-owners

@jacobmarble
Copy link
Contributor

The public InfluxDB docs do not mention nanoseconds etc as valid precision values:

Telegraf (InfluxData's own agent) apparently doesn't support the v3 write endpoint yet:

I suggest we involve InfluxData engineers before merging this change. I'll contact them directly.

@atoulme atoulme self-requested a review October 20, 2025 20:00
@StevenSeeger
Copy link
Author

The public InfluxDB docs do not mention nanoseconds etc as valid precision values:

Probably should have used this api doc: https://docs.influxdata.com/influxdb3/enterprise/api/v3/#operation/PostV2Write

It specifies the nanosecond and other inputs, which gets output as an error from the otel collector when trying to post logs to the endpoint using the current default 'ns' parameter

@jacobmarble
Copy link
Contributor

FWIW I've contacted some friends at InfluxData, and I'm sure we'll hear from them soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

InfluxDB Exporter uses unsupported ns precision instead of nanosecond for InfluxDB 3 Core

5 participants