• 1 Post
  • 6 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle


  • Yeah I think the problem with my company is that they want both things.

    That they can be able to solve easy issues following a KB and to just escalate tickets if they take a bit more time or knowledge to solve.

    We’re trying to solve the easier issues with Rundeck jobs that they can execute, but I think that will bring a new bag of issues:

    • If the Rundeck job fails, they will have to not only include the issue but also the error in the Rundeck Job
    • How can they check (or even have the knowledge) to know if the Rundeck Job worked like it should, to avoid situations where they said the issue is resolved, but then the client returns the ticket saying that nothing changed
    • If a Rundeck job needs some parameters, that may add a bigger level of knowledge for them to have, to avoid running the job on the wrong machine for example


  • Thanks a lot for that insight, I have asked current and previous members of the Team about the KPI’s and unfortunately they are clearly not alligned with ours.

    They have stuff like:

    • Don’t keep Incidents with your, only solve if it’s fast (minus 5min), else pass to the expert team
    • Can’t keep a Change for more than 5 days, even if it’s related to waiting for a client response

    They do have credentials to access servers, even with root privileges on some servers (not that we think that’s safe), but there’s a lot of infighting between their management and other Customer Teams, they’re management want them to be able to touch everything but at the same time, doesn’t invest in training and want’s the tickets to be gone fast.

    There’s also a lack of leadership and training, currently they have a week of onboarding and it’s just watching some Udemy videos.