Within that time, I have had two or three sessions from the Foglight for Databases team that briefed me on new features that have been added to the tool. By next month, I will have been working in my current field overall for four years. When using Foglight for Databases for monitoring databases, it enables me to drill down and see what's causing the issue if something doesn't look right. It has all these excellent features, ranging from the workload and IO to CPU and network, and it tells me exactly what I need to see when I drill down to the point that I need. I do not find anything I dislike about Foglight for Databases. All I think could be added is more hands-on teaching or sessions to see if they have added any new features, since we are moving more to AI and automation to ensure we are abreast with the current graphical interface. When anything comes up, they try to contact me to check a database or anything that is happening. That is one of my favorites; I log on to Foglight for Databases and then see the activities and probably see the query that is causing the issue or the database in question, or if it's the CPU or the workload or anything of that sort, and then I explain it to them. If it's a query that a dev team member is running, I can ask them to know the importance and if that could be terminated to fix the issue. I have given Foglight for Databases an overall rating of nine.
