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
Let's say a user has setup a few pipelines and enabled them.
Next, they added more and more logs from different systems and they observed many parsing errors in the collector logs. When they re-visit pipelines, they should see if the earlier pipelines are still working fine or if they are throwing errors then the pipeline list page should show some error markers so that they can edit those pipelines.
I have seen this happen for traceID ingested from different systems which do not follow the same otel semantics
The text was updated successfully, but these errors were encountered:
Let's say a user has setup a few pipelines and enabled them.
Next, they added more and more logs from different systems and they observed many parsing errors in the collector logs. When they re-visit pipelines, they should see if the earlier pipelines are still working fine or if they are throwing errors then the pipeline list page should show some error markers so that they can edit those pipelines.
I have seen this happen for traceID ingested from different systems which do not follow the same otel semantics
The text was updated successfully, but these errors were encountered: