Hi any update on the above message

On Friday, May 13, 2022 at 11:58:43 AM UTC+5:30 saipradeep bojja wrote:

> Hi Christian,
>
> I have configured the magento module able to get the metrics for Soap 
> url's with status code 200. 
> But when when ever i get a response "200". There is also an error is 
> generated in an error log.
>
> Below is the error log when i get "200" if i get "500" response i wont get 
> any error.
> [date and time] [core:eorror] [pid 9731:tid 140637200057483] (104) 
> Connection reset by peer: [client <ip>:38464] AH000574: 
> ap_content_length_filter:apr_bucket_read() failed
>
> How to resolve this am not getting any clue actually. Atleast how to 
> bypass the error.log?  would be helpfull
>
>
> On Tuesday, July 14, 2020 at 10:44:48 PM UTC+5:30 Christian Hoffmann wrote:
>
>> Hi, 
>>
>> On 7/14/20 11:17 AM, Yusuf Dönmez wrote: 
>> [...] 
>> >       - source_labels: [__address__] 
>> >         target_label: __param_target 
>> >       - source_labels: [__param_target] 
>> >         target_label: instance 
>> >       - target_label: __address__ 
>> >         replacement: 
>> [...] 
>> > - labels: 
>> >     module: magento1_x 
>> >   targets: 
>> >   - 'https://www._client_host_.com/api/v2_soap/' 
>>
>> The only thing I notice immediately is that you seem to set a label 
>> which is identical to your blackbox_exporter module (module=magento1_x), 
>> but I suspect that it is not passed to blackbox_exporter. Can you 
>> confirm via the targets on the Prometheus Web UI? I suspect there is no 
>> module=magento1_x. 
>>
>> If you don't need the module as a label in your metrics, I simply 
>> suggest to change it to __param_module: magento1_x so that it is used 
>> internally only. 
>>
>> If you do need it, I suggest adding a relabeling rule which copies the 
>> value of the module label into the __param_module special label. 
>>
>>
>> If this is not the case, I could only suspect some problem with quoting 
>> or some other headers. A tcpdump would help, but only if you are able to 
>> run this without TLS or are able to intercept it some how (mitmproxy or 
>> Wireshark + TLS secret capturing via LD_PRELOAD or something). You could 
>> also hack up blackbox_exporter to output the relevant headers if 
>> possible. 
>>
>> As far as I can see, the existing debug methods do not cover it. 
>>
>> I guess you've already tried what's listed here: 
>>
>> https://www.robustperception.io/debugging-blackbox-exporter-failures 
>>
>> Kind regards, 
>> Christian 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/7374c4f6-3237-4d29-96d3-b4256df9f8cbn%40googlegroups.com.

Reply via email to