See #60 for details
Aggregate information about historic Dagster run failures
I'm looking at a collection of Dagster run failures for a particular pipeline/job. I'd like to know whether these are all related to the same root cause.
Drilling into each run failure one by one I can see that it's the same solid failing; but this is a somewhat tedious process.
Ideas of Implementation
I'd like to be able to see a list of the failed solids associated with each failed run on the Runs screen
I'd also like to be able to search across the logs of each run; and see how many pipelines contain the same error
Message from the maintainers:
Excited about this feature? Give it a :thumbsup:. We factor engagement into prioritization.
Address #60 - Update usage instructions to fix `ERROR ReferenceError: nv is not defined at Object.bigNumberSparkline` errors
See #60 for details
commit sha： c04000428b3e8321cfde58dc1178195668e58a05push time in 1 month ago
commit sha： 667487cee7d40c6aadcab372d13c5943cacd1182push time in 2 months ago
commit sha： 87786a1e49f565d99eddc474fbd20c4596b8dd57push time in 2 months ago
commit sha： cf7f4d699f089a079817887acc834233aff6b1c0push time in 2 months ago
commit sha： 28d0421020feb83bc6a5a8cdf446a5e11ea7227apush time in 2 months ago
commit sha： 6c39055fb6a3eb51e68c01b0931aa69f21cc560fpush time in 2 months ago
commit sha： ebff6808298bc823fd59d536f1c2733b15120fcbpush time in 2 months ago
commit sha： 1a58b8a9548fb1bbc5755b7f285e3217a00567a2push time in 2 months ago
commit sha： 50f2a9f08d858d89afc998f2bb2982752d0d5eb9push time in 2 months ago
commit sha： e623f737e925ee2c5eb8017c941481b0798d3a0cpush time in 2 months ago
mrdavidlaing in cloudfoundry-community/stride-notification-resource create branch snyk-fix-073a700b5039a091410f1301430f4a76
commit sha： 224a205fcaefdc1db6462ccc9200987bb97cfb21push time in 2 months ago
commit sha： 683ffb2f1841739e8665b4ba7590e0b10a4b9254push time in 2 months ago