Replies: 3 comments
|
Hi @jjjasont, indeed we decided to remove it. We might consider adding it back if strongly requested by the community. The messages expiration is interesting actually! |
|
hey @jjjasont indeed we temporary removed that option because we thought that it was not clear how our users were using this feature and we saw many of them disable it. Can you tell me more about your usage of those traces? Are you using self hosted or cloud version? |
|
Hi @brunobuddy , I'm self hosting manifest. I use it as a middle man to route to different providers. having the message stored provide some insights on which application is sending request, what are they requesting and what are the responses. When running log job, it is helpful to be able to see the request and response to understand if it's legitimate or hallucinating. |
Uh oh!
There was an error while loading. Please reload this page.
https://github.com/mnfst/manifest/releases/tag/manifest%406.12.0
removed a very useful feature 8956f43: Stop storing full message request/response bodies.
I truely value the insight of the full message request/response bodies of the request. Instead of having the feature completely removed, can we allow the user to select a limit (days or number of request or unlimited) and manifest will purge the expired message instead?
All reactions