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
Problem
We recently upgraded tremor from 0.6.1 to 0.7.4alpha version. After upgrading we are not able to collect metrics for runtime node in port. We were able to collect metrics in the earlier version.
As part of the optimizations in the version of 0.7 and beyond we are culling nodes of the executable graph that have no impact on the pipeline. The in node for pipelines is one of those nodes. As an alternative, the onramps now include metrics, where the same value can be read from @anupdhml, can elaborate on that.
If that works for you I think we can close that otherwise, it'd be great to understand what problem you're trying to solve and see how we can solve that best.
Yes, the onramp metrics work for the need here and since the in node was never part of the pipeline config explicitly, it makes sense for metrics for it to be not present now. Chatted about this with Raj too over slack and he is fine with closing this out.
Problem
We recently upgraded tremor from
0.6.1
to0.7.4alpha
version. After upgrading we are not able to collect metrics forruntime
nodein
port. We were able to collect metrics in the earlier version.Steps
Notes
Output of
rustup --version
:Output of
rustup show
:Output of
tremor-server --version
: tremor:0.7.4-alphaThe text was updated successfully, but these errors were encountered: