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
Given the server is running
I registered a component with id "multiMetricComponent" and a metric {"multi-regex" : "some action took (\d+) ms and some other action took (\d+) ms", "metric-keys" : ["a-numerical-metric", "another-numerical-metric"]}
I do a POST with {"log" : "some action took 101 ms and some other action took 202 ms"} to /components/parsingConfiguredComponent/logs on the LogReceiver port
the response should have statuscode 202
The text was updated successfully, but these errors were encountered:
Maybe merge with the single regex logparser? Instead of a new name (multi-regex) use the same name(regex) and depending on the number of capture groups it will look for the right number of metric keys. Just a thought, lets develop in parallel and discuss after.
Given the server is running
I registered a component with id "multiMetricComponent" and a metric {"multi-regex" : "some action took (\d+) ms and some other action took (\d+) ms", "metric-keys" : ["a-numerical-metric", "another-numerical-metric"]}
I do a POST with {"log" : "some action took 101 ms and some other action took 202 ms"} to /components/parsingConfiguredComponent/logs on the LogReceiver port
the response should have statuscode 202
The text was updated successfully, but these errors were encountered: