1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Good to receive this proposal. Could you clarify the requirement, make sure I understand correctly and see if there is workaround.
The trace data to be separated is from a single application or different applications?
- If from different applications, the solution is by setup multiple otel collectors with different IAM role/credentials. So trace data can be emitted to different account and use different sampling rules.
- If from a single application, though I think mostly single application does not make sense, can use filterprocessor to dispatch trace data to different awsxray exporters. The sampling rules have to be in one account because collector supports just one awsproxy extension.
service:
pipelines:
traces:
receivers: [otlp]
processors: [filterprocessor]
exporters: [awsxray]
traces/2:
receivers: [otlp]
processors: [filterprocessor/2]
exporters: [awsxray/2]
回答済み 2年前
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 1年前