datadog metrics

[Fanbin Bu]

Hi,

Has anybody seen this error before and what is the suggested way to solve it?

2020-03-07 02:54:34,100 WARN  org.apache.flink.metrics.datadog.DatadogHttpClient            - Failed to send request to Datadog (response was Response{protocol=http/1.1, code=413, message=Request Entity Too Large, url=https://app.datadoghq.com/api/v1/series?api_key=

thanks,

Fanbin

[Fanbin Bu]

quote from the following link:

http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/SQL-Query-named-operator-exceeds-80-characters-td24807.html#a24818

"This is a safeguard in the metric system to prevent extremely long names
(as these could cause the reporting to fail); so long as the prefix is
unique you can safely ignore this warning."

I do see from log that my sql operator name is too long and says it's truncated.

But i still failed to report to datadog.

Thanks

Fanbin

On Sun, Mar 8, 2020 at 11:36 PM Fanbin Bu <[hidden email]> wrote:

Hi,

Has anybody seen this error before and what is the suggested way to solve it?

2020-03-07 02:54:34,100 WARN  org.apache.flink.metrics.datadog.DatadogHttpClient            - Failed to send request to Datadog (response was Response{protocol=http/1.1, code=413, message=Request Entity Too Large, url=https://app.datadoghq.com/api/v1/series?api_key=

thanks,

Fanbin

[Chesnay Schepler]

Please open a JIRA; we may have to split the datatog report into several chunks.

On 09/03/2020 07:47, Fanbin Bu wrote:

quote from the following link:

http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/SQL-Query-named-operator-exceeds-80-characters-td24807.html#a24818

"This is a safeguard in the metric system to prevent extremely long names
(as these could cause the reporting to fail); so long as the prefix is
unique you can safely ignore this warning."

I do see from log that my sql operator name is too long and says it's truncated.

But i still failed to report to datadog.

Thanks

Fanbin

On Sun, Mar 8, 2020 at 11:36 PM Fanbin Bu <[hidden email]> wrote:

Hi,

Has anybody seen this error before and what is the suggested way to solve it?

2020-03-07 02:54:34,100 WARN  org.apache.flink.metrics.datadog.DatadogHttpClient            - Failed to send request to Datadog (response was Response{protocol=http/1.1, code=413, message=Request Entity Too Large, url=https://app.datadoghq.com/api/v1/series?api_key=

thanks,

Fanbin

[Steve Whelan]

Hi Fabian,

We ran into the same issue. We modified the reporter to emit the metrics in chunks and it worked fine after. Would be interested in seeing a ticket on this as well.

- Steve 

On Wed, Mar 11, 2020 at 5:13 AM Chesnay Schepler <[hidden email]> wrote:

Please open a JIRA; we may have to split the datatog report into several chunks.

On 09/03/2020 07:47, Fanbin Bu wrote:

quote from the following link:

http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/SQL-Query-named-operator-exceeds-80-characters-td24807.html#a24818

"This is a safeguard in the metric system to prevent extremely long names
(as these could cause the reporting to fail); so long as the prefix is
unique you can safely ignore this warning."

I do see from log that my sql operator name is too long and says it's truncated.

But i still failed to report to datadog.

Thanks

Fanbin

On Sun, Mar 8, 2020 at 11:36 PM Fanbin Bu <[hidden email]> wrote:

Hi,

Has anybody seen this error before and what is the suggested way to solve it?

2020-03-07 02:54:34,100 WARN  org.apache.flink.metrics.datadog.DatadogHttpClient            - Failed to send request to Datadog (response was Response{protocol=http/1.1, code=413, message=Request Entity Too Large, url=https://app.datadoghq.com/api/v1/series?api_key=

thanks,

Fanbin

[Chesnay Schepler]

I've created https://issues.apache.org/jira/browse/FLINK-16611.

@Steva Any chance you could contribute your changes, or some insight on what would need to be changed?

On 11/03/2020 23:16, Steve Whelan wrote:

Hi Fabian,

We ran into the same issue. We modified the reporter to emit the metrics in chunks and it worked fine after. Would be interested in seeing a ticket on this as well.

- Steve 

On Wed, Mar 11, 2020 at 5:13 AM Chesnay Schepler <[hidden email]> wrote:

Please open a JIRA; we may have to split the datatog report into several chunks.

On 09/03/2020 07:47, Fanbin Bu wrote:

quote from the following link:

http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/SQL-Query-named-operator-exceeds-80-characters-td24807.html#a24818

"This is a safeguard in the metric system to prevent extremely long names
(as these could cause the reporting to fail); so long as the prefix is
unique you can safely ignore this warning."

I do see from log that my sql operator name is too long and says it's truncated.

But i still failed to report to datadog.

Thanks

Fanbin

On Sun, Mar 8, 2020 at 11:36 PM Fanbin Bu <[hidden email]> wrote:

Hi,

Has anybody seen this error before and what is the suggested way to solve it?

2020-03-07 02:54:34,100 WARN  org.apache.flink.metrics.datadog.DatadogHttpClient            - Failed to send request to Datadog (response was Response{protocol=http/1.1, code=413, message=Request Entity Too Large, url=https://app.datadoghq.com/api/v1/series?api_key=

thanks,

Fanbin

[Fanbin Bu]

Hi Steve,

could you please share your work around solution in more detail in the above ticket?

Thanks,

Fanbin

On Mon, Mar 16, 2020 at 2:50 AM Chesnay Schepler <[hidden email]> wrote:

I've created https://issues.apache.org/jira/browse/FLINK-16611.

@Steva Any chance you could contribute your changes, or some insight on what would need to be changed?

On 11/03/2020 23:16, Steve Whelan wrote:

Hi Fabian,

We ran into the same issue. We modified the reporter to emit the metrics in chunks and it worked fine after. Would be interested in seeing a ticket on this as well.

- Steve 

On Wed, Mar 11, 2020 at 5:13 AM Chesnay Schepler <[hidden email]> wrote:

Please open a JIRA; we may have to split the datatog report into several chunks.

On 09/03/2020 07:47, Fanbin Bu wrote:

quote from the following link:

http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/SQL-Query-named-operator-exceeds-80-characters-td24807.html#a24818

"This is a safeguard in the metric system to prevent extremely long names
(as these could cause the reporting to fail); so long as the prefix is
unique you can safely ignore this warning."

I do see from log that my sql operator name is too long and says it's truncated.

But i still failed to report to datadog.

Thanks

Fanbin

On Sun, Mar 8, 2020 at 11:36 PM Fanbin Bu <[hidden email]> wrote:

Hi,

Has anybody seen this error before and what is the suggested way to solve it?

2020-03-07 02:54:34,100 WARN  org.apache.flink.metrics.datadog.DatadogHttpClient            - Failed to send request to Datadog (response was Response{protocol=http/1.1, code=413, message=Request Entity Too Large, url=https://app.datadoghq.com/api/v1/series?api_key=

thanks,

Fanbin

[Steve Whelan]

Hi Fanbin,

I have commented on the ticket: https://issues.apache.org/jira/browse/FLINK-16611.

- Steve

On Mon, Mar 16, 2020 at 6:39 PM Fanbin Bu <[hidden email]> wrote:

Hi Steve,

could you please share your work around solution in more detail in the above ticket?

Thanks,

Fanbin

On Mon, Mar 16, 2020 at 2:50 AM Chesnay Schepler <[hidden email]> wrote:

I've created https://issues.apache.org/jira/browse/FLINK-16611.

@Steva Any chance you could contribute your changes, or some insight on what would need to be changed?

On 11/03/2020 23:16, Steve Whelan wrote:

Hi Fabian,

We ran into the same issue. We modified the reporter to emit the metrics in chunks and it worked fine after. Would be interested in seeing a ticket on this as well.

- Steve 

On Wed, Mar 11, 2020 at 5:13 AM Chesnay Schepler <[hidden email]> wrote:

Please open a JIRA; we may have to split the datatog report into several chunks.

On 09/03/2020 07:47, Fanbin Bu wrote:

quote from the following link:

http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/SQL-Query-named-operator-exceeds-80-characters-td24807.html#a24818

"This is a safeguard in the metric system to prevent extremely long names
(as these could cause the reporting to fail); so long as the prefix is
unique you can safely ignore this warning."

I do see from log that my sql operator name is too long and says it's truncated.

But i still failed to report to datadog.

Thanks

Fanbin

On Sun, Mar 8, 2020 at 11:36 PM Fanbin Bu <[hidden email]> wrote:

Hi,

Has anybody seen this error before and what is the suggested way to solve it?

2020-03-07 02:54:34,100 WARN  org.apache.flink.metrics.datadog.DatadogHttpClient            - Failed to send request to Datadog (response was Response{protocol=http/1.1, code=413, message=Request Entity Too Large, url=https://app.datadoghq.com/api/v1/series?api_key=

thanks,

Fanbin