apm reporter?

Submitted by cesar.ribeiro_1... on Mon, 06/01/2020 - 16:39
1
0
-1

Hello,

I'm receiving several of those messages in server's log:

Jun 1 13:20:50 dockerh12 bonita_urb_hom_7_9[41124] 2020-06-01 10:20:50.010 [apm-reporter] INFO co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Backing off for 36 seconds (+/-10%)
Jun 1 13:21:25 dockerh12 bonita_urb_hom_7_9[41124] 2020-06-01 10:21:25.123 [apm-reporter] ERROR co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Error sending data to APM server: Server returned HTTP response code: 503 for URL: http://10.151.6.186:8200/intake/v2/events, response code is 503
Jun 1 13:21:25 dockerh12 bonita_urb_hom_7_9[41124] 2020-06-01 10:21:25.123 [apm-reporter] WARN co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - {
Jun 1 13:21:25 dockerh12 bonita_urb_hom_7_9[41124] "accepted": 0,
Jun 1 13:21:25 dockerh12 bonita_urb_hom_7_9[41124] "errors": [
Jun 1 13:21:25 dockerh12 bonita_urb_hom_7_9[41124] {
Jun 1 13:21:25 dockerh12 bonita_urb_hom_7_9[41124] "message": "queue is full"
Jun 1 13:21:25 dockerh12 bonita_urb_hom_7_9[41124] }
Jun 1 13:21:25 dockerh12 bonita_urb_hom_7_9[41124] ]
Jun 1 13:21:25 dockerh12 bonita_urb_hom_7_9[41124] }
Jun 1 13:21:25 dockerh12 bonita_urb_hom_7_9[41124] ]

I don't know the cause. Can anyone help?

If "apm reporter" isn't vital to the engine, is it possible to maybe disable it?

Thanks in advance.

1 answer

Submitted by cesar.ribeiro_1... on Mon, 06/01/2020 - 20:20
1
0
-1
This one is the BEST answer!

Sorry, found that it's not Bonita BPM related.

Notifications