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

Issue with alloy convert #2036

Open
lijin-jayan opened this issue Nov 5, 2024 · 0 comments
Open

Issue with alloy convert #2036

lijin-jayan opened this issue Nov 5, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@lijin-jayan
Copy link

What's wrong?

When we tried to convert the Grafana agent config using alloy convert we got below errors. Since we have lot of machines running with different configs, we were planning to migrate using alloy convert in ansible playbook, but however it seems alloy convert will not work.

Error) The service_graphs processor for traces has no direct Alloy equivalent. This configuration appends metrics to the /metrics endpoint of the agent which is not possible in Alloy. Alternatively, you can use the otelcol.connector.servicegraph component to build a pipeline which generates and forwards service graph metrics.
(Error) automatic_logging for traces has no direct Alloy equivalent. A best effort translation can be made which only outputs to stdout and not directly to loki by bypassing errors.
(Error) Cannot convert using configuration including spanmetrics handler_endpoint. No equivalent exists for exposing a known /metrics endpoint. You can use metrics_instance instead to enabled conversion.
Error) The converter does not support converting the provided wal_cleanup_age metrics config.
(Error) The converter does not support converting the provided wal_cleanup_period metrics config.

Steps to reproduce

Error) The service_graphs processor for traces has no direct Alloy equivalent. This configuration appends metrics to the /metrics endpoint of the agent which is not possible in Alloy. Alternatively, you can use the otelcol.connector.servicegraph component to build a pipeline which generates and forwards service graph metrics.
(Error) automatic_logging for traces has no direct Alloy equivalent. A best effort translation can be made which only outputs to stdout and not directly to loki by bypassing errors.
(Error) Cannot convert using configuration including spanmetrics handler_endpoint. No equivalent exists for exposing a known /metrics endpoint. You can use metrics_instance instead to enabled conversion.
Error) The converter does not support converting the provided wal_cleanup_age metrics config.
(Error) The converter does not support converting the provided wal_cleanup_period metrics config.

### System information

RHEL 9

### Software version

_No response_

### Configuration

_No response_

### Logs

Error) The service_graphs processor for traces has no direct Alloy equivalent. This configuration appends metrics to the /metrics endpoint of the agent which is not possible in Alloy. Alternatively, you can use the otelcol.connector.servicegraph component to build a pipeline which generates and forwards service graph metrics.
(Error) automatic_logging for traces has no direct Alloy equivalent. A best effort translation can be made which only outputs to stdout and not directly to loki by bypassing errors.
(Error) Cannot convert using configuration including spanmetrics handler_endpoint. No equivalent exists for exposing a known /metrics endpoint. You can use metrics_instance instead to enabled conversion.
Error) The converter does not support converting the provided wal_cleanup_age metrics config.
(Error) The converter does not support converting the provided wal_cleanup_period metrics config.

@lijin-jayan lijin-jayan added the bug Something isn't working label Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant