We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To make the deployment trace better readable, it should be restructured and look as follows in the future:
Furthermore, Task and evaluation results should be represented in the Trace to see the following information:
Definition of done
#388 (comment)
The text was updated successfully, but these errors were encountered:
LGTM. We should also a specific type for the traces so people can distinguish them from "regular" application traces.
Also we might get back some of the semantics of the Keptn events as well.
Overall, this will be much better than the current span naming
Sorry, something went wrong.
thisthat
No branches or pull requests
To make the deployment trace better readable, it should be restructured and look as follows in the future:
Furthermore, Task and evaluation results should be represented in the Trace to see the following information:
Definition of done
#388 (comment)
The text was updated successfully, but these errors were encountered: