You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In order to build a PxL script to show LET metrics, we need to know if a query had errored to determine the error rate. At the moment, the response status / body of a record is ok: number double ....
The wire protocol for mongo doesn't show a clear way to determine the status of a query but it seems like there are certain error codes that are sent by the database in the event of an error. An additional key/value pair (e.g. errmsg: error code #) would be added to the BSON of the response frame as per mongo source code.
Describe the solution you'd like
I tried forcing an error status between a local client/database setup and was able to generate a pcap of the errmsg key in the response frame. This key is notably not at the top level of the document in the response payload whereas the ok key is.
I believe one way to go about this is by having the parser search for an errmsg string in the logic handling a response frame before searching for the ok key. In the event of an error, the response status would then contain the errmsg key and its associated error code.
Describe alternatives you've considered
To generate LET metrics, it could also be possible to search/pluck an errmsg key from PxL on a response to see if a query had errored.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In order to build a PxL script to show LET metrics, we need to know if a query had errored to determine the error rate. At the moment, the response status / body of a record is
ok: number double ...
.The wire protocol for mongo doesn't show a clear way to determine the status of a query but it seems like there are certain error codes that are sent by the database in the event of an error. An additional key/value pair (e.g.
errmsg: error code #
) would be added to the BSON of the response frame as per mongo source code.Describe the solution you'd like
I tried forcing an error status between a local client/database setup and was able to generate a pcap of the
errmsg
key in the response frame. This key is notably not at the top level of thedocument
in the response payload whereas theok
key is.I believe one way to go about this is by having the parser search for an
errmsg
string in the logic handling a response frame before searching for theok
key. In the event of an error, the response status would then contain theerrmsg
key and its associated error code.Describe alternatives you've considered
To generate LET metrics, it could also be possible to search/pluck an
errmsg
key from PxL on a response to see if a query had errored.The text was updated successfully, but these errors were encountered: