-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Support additional exporters for exporting collector metrics #7641
Comments
5 tasks
One thing I liked about vector was its internal_metrics source, which in collector terms would be a receiver that would output its metrics that can be processed by a normal processing pipeline, rather than needing a localhost network hop |
codeboten
pushed a commit
that referenced
this issue
Jul 14, 2023
This enables end users to configure additional prometheus exporters for the collector's telemetry via the `readers` configuration option. Configuring prometheus through the existing method of setting the service::metrics::address will continue to work, and only log a warning for users who have enabled the `telemetry.useOtelWithSDKConfigurationForInternalTelemetry` feature gate. Linked issue: #7641 --------- Signed-off-by: Alex Boten <aboten@lightstep.com> Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com>
codeboten
pushed a commit
to codeboten/opentelemetry-collector
that referenced
this issue
Jul 14, 2023
Internal metrics can now be additionally configure to export using the stdout exporter. Linked issue: open-telemetry#7641 Signed-off-by: Alex Boten <aboten@lightstep.com>
codeboten
pushed a commit
to codeboten/opentelemetry-collector
that referenced
this issue
Jul 14, 2023
Internal metrics can now be additionally configure to export using the stdout exporter. Linked issue: open-telemetry#7641 Signed-off-by: Alex Boten <aboten@lightstep.com>
codeboten
pushed a commit
to codeboten/opentelemetry-collector
that referenced
this issue
Jul 14, 2023
Internal metrics can now be additionally configure to export using the stdout exporter. Linked issue: open-telemetry#7641 Signed-off-by: Alex Boten <aboten@lightstep.com>
codeboten
pushed a commit
to codeboten/opentelemetry-collector
that referenced
this issue
Jul 14, 2023
Internal metrics can now be additionally configure to export using the stdout exporter. Linked issue: open-telemetry#7641 Signed-off-by: Alex Boten <aboten@lightstep.com>
codeboten
pushed a commit
to codeboten/opentelemetry-collector
that referenced
this issue
Jul 14, 2023
Internal metrics can now be additionally configure to export using the stdout exporter. Linked issue: open-telemetry#7641 Signed-off-by: Alex Boten <aboten@lightstep.com>
codeboten
pushed a commit
to codeboten/opentelemetry-collector
that referenced
this issue
Jul 14, 2023
Internal metrics can now be additionally configure to export using the stdout exporter. Linked issue: open-telemetry#7641 Signed-off-by: Alex Boten <aboten@lightstep.com>
codeboten
pushed a commit
that referenced
this issue
Jul 17, 2023
Internal metrics can now be additionally configure to export using the stdout exporter. Linked issue: #7641 --------- Signed-off-by: Alex Boten <aboten@lightstep.com>
This was referenced Jul 17, 2023
codeboten
pushed a commit
that referenced
this issue
Jul 17, 2023
This adds support for configuring `timeout` and `interval` options for the periodic metric exporter. Linked issue: #7641 Signed-off-by: Alex Boten <aboten@lightstep.com>
codeboten
pushed a commit
that referenced
this issue
Jul 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: