Developers may need to analyze reports but don't know exactly what they need; rather they know something bad is happening. At minimum they might know that e.g., "the process is running out of memory." we want to create optimized solutions to specific problems.
Provide some way for a user to describe a problem (perhaps from a list of options), then rtk will use its facilities to help solve the issue. this might involve generating a reusable configuration which can then be subsequently applied to more reports, or maybe it's configs alongside the rtk:recommended config. (note: rtk:recommended might not be useful)
boneskull
commented
5 years ago
Maybe this is something like a "wizard".
Developers may need to analyze reports but don't know exactly what they need; rather they know something bad is happening. At minimum they might know that e.g., "the process is running out of memory." we want to create optimized solutions to specific problems.
Provide some way for a user to describe a problem (perhaps from a list of options), then rtk will use its facilities to help solve the issue. this might involve generating a reusable configuration which can then be subsequently applied to more reports, or maybe it's configs alongside the
rtk:recommendedconfig. (note:rtk:recommendedmight not be useful)