Tim, Jun 1, 2021 9:50:17 AM Tim Düsterhus <t...@bastelstu.be>:
> Aleks, > > On 6/1/21 1:03 AM, Aleksandar Lazic wrote: >>>> srv_conn([<backend>/]<server>) : integer >>>> Returns an integer value corresponding to the number of currently >>>> established >>>> connections on the designated server, possibly including the connection >>>> being >>>> @@ -17514,6 +17509,9 @@ stopping : boolean >>>> str(<string>) : string >>>> Returns a string. >>>> >>>> +stream_uniq_id : integer >>>> + Returns the uniq stream id. >>>> + >>> >>> This explanation is not useful to the reader (even I don't understand it). >> […] >> This is shown on the SPOE log line as sid and therefore I think it should be >> possible to get the same ID also within HAProxy as fetch method. >> ``` >> SPOE: [agent-on-http-req] <EVENT:on-frontend-http-request> sid=88 st=0 >> 0/0/0/0/0 1/1 0/0 10/33 >> ``` >> […] >> ``` >> This fetch method returns the internal Stream ID, if a stream is available. >> The >> internal Stream ID is used in several places in HAProxy to trace the Stream >> inside HAProxy. It is also uses in SPOE as "sid" value. >> ``` >> > > This phrasing is understandable to me, but now I'm wondering if this is the > best solution. Maybe the already existing user-configurable unique request ID > should instead be sent to the SPOE and then logged? > > https://cbonte.github.io/haproxy-dconv/2.2/configuration.html#7.3.6-unique-id > > The request_counter (%rt) you mentioned could be embedded into this unique-id. Well this uniqe-id is not send as Stream ID to SPOA receiver, due to this fact can't you debug which stream is the troubled one. > Best regards > Tim Düsterhus Regards Alex
