You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I run into an issue where the error message tells me to look through the logs for a specific TraceID, I have to open a ticket, create a support bundle, hand over the bundle and the right TraceID to Support and wait x amount of time before support can tell me what the issue is and start me on resolving the issue. On top of that, once resolved if another TraceID comes out of the retest, I am repeating the process. This is evident is trying to connect CD4PE V5 to Puppet Enterprise. The first TraceID was because we could not curl from the CD4PE server to the PE server for the Classification port 4433. Once that was resolved, I am now waiting on a resolution for the second TraceID. Total time lost... at least 3 days.
Describe the Solution You Would Like
I would like a bolt plan that I run from the bolt server that contains the Trace ID and it returns the appropriate information in the many logs around what is wrong and a possible solution. This allows me to remove simple problems or stupid mistakes from the troubleshooting process and allows me to make better use of supports time.
Describe Alternatives You've Considered
The simple alternative would be to provide better error messages instead of a TraceID. But as a fellow programmer, I get why that might not be the case. Another alternative might a be an admin console that has access to the logs on the back end where I can put in the Trace ID and get the relevant information.
Additional Context
I'm looking to speed up the process of "I have an error, what's wrong and what can I do to ensure its really a problem I need supports help for before submitting said request."
The text was updated successfully, but these errors were encountered:
Use Case
If I run into an issue where the error message tells me to look through the logs for a specific TraceID, I have to open a ticket, create a support bundle, hand over the bundle and the right TraceID to Support and wait x amount of time before support can tell me what the issue is and start me on resolving the issue. On top of that, once resolved if another TraceID comes out of the retest, I am repeating the process. This is evident is trying to connect CD4PE V5 to Puppet Enterprise. The first TraceID was because we could not curl from the CD4PE server to the PE server for the Classification port 4433. Once that was resolved, I am now waiting on a resolution for the second TraceID. Total time lost... at least 3 days.
Describe the Solution You Would Like
I would like a bolt plan that I run from the bolt server that contains the Trace ID and it returns the appropriate information in the many logs around what is wrong and a possible solution. This allows me to remove simple problems or stupid mistakes from the troubleshooting process and allows me to make better use of supports time.
Describe Alternatives You've Considered
The simple alternative would be to provide better error messages instead of a TraceID. But as a fellow programmer, I get why that might not be the case. Another alternative might a be an admin console that has access to the logs on the back end where I can put in the Trace ID and get the relevant information.
Additional Context
I'm looking to speed up the process of "I have an error, what's wrong and what can I do to ensure its really a problem I need supports help for before submitting said request."
The text was updated successfully, but these errors were encountered: