Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Konrad Pilch
2,435 PointsCan somebody help me with this?
(b) Discuss the importance of logging faults and the need to keep a log of all faults that are received within the department. Include what would happen if faults are not logged and what are the consequences. Include: You need to include using fault logs for future reference, creating a solutions database from them, creating reports from them, analysing technicians’ workload, identifying trends, planning future workload, monitoring performance of the department etc.
(c) There are many recent advancements in support technology, you need to research and review one recent advance in support systems technology. Any innovations used must be less than 5 years old.
And what are
System logs,
and Free PC Audit ?
Could somebody explain it more human friendly? not form microsoft page please
1 Answer
James Lake
8,469 PointsHi Konrad,
What's the wider context of these questions (I feel like this is homework of some description).
Part B - It seems like they are referring to faults as issues reported to something like a help desk department. So the questions is about information management or, mismanagement. If you think about issues and fixes as information that has value. If you take the treehouse forum as an example there's a log of valuable information here for both users and Treehouse. Because the forum is public is 50 people have the same problem but someone has posed (logged) a solution then that's a lot of time saved. If lots of people are reporting the same issue then it becomes easy to identify patterns about something being not working correctly(if it was submitted privately to individual support people who didn't talk then you'd lose the big picture of what's going on). The other points your part B question raises are valid, if your team spends 80% of their time on one thing, and 20% of every other area, then you can easily see where you want to start looking for efficiencies.
Part C - Depending on context, could be tools techs can use to support users, or it could be tools techs can use to get better information about a system so the support team is better informed ie levels of system monitoring and analytics.
System logs - sometimes referring to logfiles - a log of process running on a system. Useful for fault finding, or understanding how a system works. Also used for legal reasons. PC Audit - most likely is referring to software that provides an audit of hardware and software running on a computer. You'd use something like this for security, performance, maintenance etc
Hopefully this is of some help to you.