You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: