topic Re: Not able to ingest data in EF2 extension in Extensions

Not able to ingest data in EF2 extension

AntonioSousa — Tue, 24 Sep 2024 05:48:35 GMT

I'm converting an EF1 extension to EF2, but not able to ingest certain data. The error is below.

It seems to me that this might be a limitation because EF2 seems to internally use the Line Protocol, and eventually not supporting dimensions with capital letters, which were supported before. Is this the case?

[131d4cad-c83e-3ab5-9cd2-bd685ab76d1d][1306936874558483997][4860][out]2024-09-20 00:20:48,878 [WARNING] api (ThreadPoolExecutor-1_0): Error HTTP 400 from http://127.0.0.1:14599/mint/1306936874558483997: b'{\n "error": {\n "invalidLines": [\n {\n "line": 15,\n "error": "invalid dimension key in message \'enqueued_messages,ChannelName=\\"AS_123_IN\\" gauge,0.0 172678796669\'; error at \'C\' (index 18)"\n }, ... ],\n "code": 400,\n "message": "12 invalid lines"\n },\n "linesOk": 14,\n "linesInvalid": 12\n}'

Re: Not able to ingest data in EF2 extension

JamesKitson — Fri, 20 Sep 2024 07:58:58 GMT

Yes, extensions use the metric ingestion protocol which only allows lowercase characters in the dimension keys:

https://docs.dynatrace.com/docs/shortlink/metric-ingestion-protocol#dimension

Re: Not able to ingest data in EF2 extension

AntonioSousa — Fri, 20 Sep 2024 08:52:22 GMT

@JamesKitson,

So that means that what is now working in EF1 will stop working with EF2?

Re: Not able to ingest data in EF2 extension

Julius_Loman — Fri, 20 Sep 2024 08:57:00 GMT

@AntonioSousa this is true, also ran into this, luckily I did not have to provide a data continuity.

Previously metric ingestion was not based on MINT and it allowed uppercase letters in dimension keys. MINT does not allow this. You can still define metric metadata, but in metric selector it must be lowercase.

Re: Not able to ingest data in EF2 extension

AntonioSousa — Fri, 20 Sep 2024 09:18:13 GMT

@Julius_Loman,

Yes I understood this yesterday. Lost some hours figuring it out 😞

Unfortunately, it's one more not supported and non documented scenario in the EF1 to EF2 transition...