Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Diagnostic Center API, I would like my AI agent to be able to assist me in error tracing

    Scheduled Pinned Locked Moved Support
    2 Posts 2 Posters 4 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C Offline
      carl.westman_8110
      last edited by

      Hi there!

      I've had to work with the Diagnostic Center lately and it's been a hassle to copy paste messages from the GUI to my AI agent.

      I've tried to find ways for my agent to get access directly to all logs and error messages but it does not seem to be natively in the API?

      Do you have any workaround or would it be possible to add this to the API? :) I think a lot of information is missed when I manually have to give it to my agent when fault tracing.

      Cheers
      Carl

      https://github.com/Wesztman

      stevedennisS 1 Reply Last reply Reply Quote
      • stevedennisS Online
        stevedennis inedo-engineer @carl.westman_8110
        last edited by

        Hi @carl.westman_8110 ,

        I think we'd recommend a work-around of just asking us for help :)

        Based on other customers who've tried to use AI to help with ProGet issues, I think you'll be spending too much time spinning your wheels. The AI guidance is almost always wrong, because the pattern-matching stack traces that were scraped from Stack Overflow are to fix coding errors. That, and we fix errors really fast, so even if it scraped an answer, it probably was an old version.

        Sometimes it makes matters worse; we saw AI guide one user to do all these strange database changes (connection string, adding indexes, etc) -- when the underlying issue was totally unrelated.

        The information in the Diagnostic Center serves two purposes:

        1. For end-users (i.e. you) to spot obvious error conditions due to misconfiguration, network errors, etc.
        2. For engineers (i.e. us) to troubleshoot, identify bugs, etc. resulting from problems you can't figure out

        It is not to proactively check for health, etc. It's only to troubleshoot known issues. And if the issue is not obvious to you, then we can help answer. Our goal is to make this as obvious as possible.

        Thanks,
        Steve

        1 Reply Last reply Reply Quote

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation