Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is InfluxDbOutputWriter still considered experimental? #159

Closed
aakarshg opened this issue Mar 23, 2022 · 3 comments
Closed

Is InfluxDbOutputWriter still considered experimental? #159

aakarshg opened this issue Mar 23, 2022 · 3 comments

Comments

@aakarshg
Copy link

Hello, We are evaluating using the InfluxDbOutputWriter for our usecase. This seems to have been added around ~6 years ago 04e4887, and I dont see any open issues nor closed issues that mentioned problems with the writer. Is it safe to use this writer in production?

@aakarshg
Copy link
Author

Tagging @cyrille-leclerc as you seemed to be the most active contributor previously :)

@cyrille-leclerc
Copy link
Member

Hello @aakarshg , thanks for looking at the jmxtrans-agent. I have never used InfluxDB and thus never used the InfluxDbOutputWriter but the code of the InfluxDbOutputWriter looked very good and nobody reported problems so I would be confident.

Another scenario could be to instrument your application with OpenTelemetry (traces, metrics, and logs) and to export the metrics to InfluxDB using the OpenTelemetry Collector exporter for InfluxDB.

@aakarshg
Copy link
Author

aakarshg commented Apr 1, 2022

Thanks for the quick reply @cyrille-leclerc :) We require a java agent implementation for our use case so jmxtrans-agent fits the bill perfectly, only concern was around the experimental tag on the InfluxDbOutputWriter.

Closing this issue, since the question has been answered.

@aakarshg aakarshg closed this as completed Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants