Metric Extraction - Settings (log) vs OpenPipeline

[y_buccellato]

Does the Metric Extraction in Settings Classic > Logs, is overwritten when we create a OpenPipeline processing the same data underneath that metric created first in Setting Classic?

Example:

I create a Metric Extraction from logs in Setting Classic matching log.source == "A", then I create a pipeline that works by  matching log.source == "A". Will the metric stay or disappear?

[Christophe_N]

Hi,

Only one pipeline can be used . 
If you select to route your data to a Pipeline in Openpipeline , it will not go through ClassicPipeline any more 

Metric will never disappear, datapoints will stay

asfaik, if you name the metric with same metric key in both pipeline, the metric will be same and it should not visible to you which is the pipeline used 🙂 
Regards,

Christophe

[y_buccellato]

Hello Chris, I will let you know about the overlapping metric from classic and Openpipeline 🙂

About the data I was told by Dynatrace that OpenPipeline takes precedence over classic pipeline, which in turns mean: if you had something  configured in Settings Classic for Log Metric Extraction and you rout the data to an OpenPipeline then you'll be stealing data from that original rule in setting classic.

[Christophe_N · Accepted solution]

Great, I got same challenge, it's working if you keep same metric key ....

just take care about uppercase / lowercase -- (here it's experience which talks 😂)
Christophe