New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jaeger based storage for activity monitoring #4011
Comments
If we move to jaeger, there seem to be ongoing work around badger storage: jaegertracing/jaeger#760 |
@chirino Do you still plan to work on this? |
Current status Still Pending: |
It might be worth waiting until openshift template based installed don't need to be supported anymore so that we can have a more dynamic operator. |
This is now completed:
|
Do we fallback to the current activity logging when jaeger is not enabled? |
No. If you enable the jaeger addon, the system will be configured for jaeger |
We also need to do some work to also enable this feature to work when camel-k mode is enabled. Not sure if camel-k support is a must have or not. |
Yes, but what if jaeger is not enabled? |
if you don't enable the jaeger addon, then syndesis continues to use db based activity logging. |
Migrated to https://issues.jboss.org/browse/ENTESB-11516 |
See also https://issues.jboss.org/browse/ENTESB-11516
This is a...
Description
As discussed in #3922 (and #3337, #3252, #2598, #1780, ...) we need a new mechanism for storing activity entries.
The text was updated successfully, but these errors were encountered: