WEEK 1: ENTRY 3

At my internship today, I was introduced briefly to what my project for the summer is going to be. Basically, I will be working on a System Log project in the next nine weeks. I learned that system logs are basically records of activities related to a specific server/ virtual machine in a specific period of time. These activities range from logins, authorizations etc. To be specific, my project will focus on auth logs, which are a type of system logs that contain system authorization and information including user logins and authentication mechanisms that were used. The firm uses virtual machines that require their auth logs to be recorded and tracked in order to ensure that they are up and running and incase of any downtime, these logs will be accessed to troubleshoot the issue. Thus, my main focus is to develop an application that will query specific critical auth logs (logs from certain servers) from Big Query, a Google Cloud Platform, and generate a report of those logs. 


These technologies and terms are very foreign to me as they might be to you because  I barely have any idea how working on these technology tools will look like or what they are used for. However, I am both excited and a little nervous about my project. Prior to the meeting, I did some research on virtualization and containerization because I thought those were the core parts of my project, but I was totally wrong. I was met with astonishment when all these new terms were introduced. However, I took notes and I intend to read documentations and articles on system logs, especially auth logs and learn more on some of these tech tools. So too, I will be using a completely different language called Go Programming. And again, I have no skills with this programming knowledge. I wish I had learned and practiced Go before today, however that was not possible because I procrastinated. Therefore, I will be spending my next days and weeks learning the Go programming language and getting myself familiarized with the tools that I will use with to develop my project.

 

Comments

Post a Comment

Popular posts from this blog

WEEK 4: ENTRY 3

  Today at my internship, I was assigned the issue of troubleshooting why my GET request Golang code is unable to generate the data from my http server. Since it was a combination of k8s deployment and Golang go, it was trickier and harder than I envisioned. The k8s was mainly used to orchestrate the objects that are needed to generate keytab from my pods. After several debugging: comparing and contrast the referred file I used as a source code coupled with looking up the errors on Stack flow (suggested me to delete my deployment and redeployed), I was still unable to fix the issue. Partly was because I did not understand what the error message was pointing at. Thus, I had to consult a member of the k8s team, who figured out that my deployment.yaml file was missing some configurations that needed to generate my key-tab. Simply, I needed the key-tab in order to be able to make the HTTP Get Request get my desired data.   Although the recommended solution from my consultation wor...
Read more

WEEK 6: ENTRY 3

  At my internship today, I continued unmarshalling the Json data I got back from Big Query API. Having tried replicating the data on the Go playground and using the Go unmarshall function yesterday, I did develop a better understanding of the json structure. I used Go’s struct to do the unmarshalling. Unlike the json data I got from my query, the documentation’s json data does not have any schema metadata and so I thought the same approach would not work. Little did I know that the schema data can be ignored when unmarshalling json data and that you can only concentrate on the part of the Json you want to unmarshall. When I consulted my buddy, he hopped on a zoom call with me and we did pair programming. I was the driver while he was the navigator, basically explaining what we were doing because he has more knowledge on Go and Json data manipulation. Working with him gave me more skills and confidence in what I was doing. He helped in not just using the Go struct, but also in tryi...
Read more

WEEK 7: ENTRY 1

  It sometimes feels like we are not good enough when our tries don’t work. Well at my internship today, I worked on resolving the json unmarshalling issue I was stuck with last Friday. After several back-and-forth consultations with my buddy and manager, I finally got a better understanding of how they wanted me to present the data. Basically, the data should be in a simple json array that could be manipulated easier. This is because as the json comes in key:pair format, I would need to extract all the keys and use those keys to send an HTTPS request to Elasticsearch Rest API.  Even though the approach was well defined and clear to me, I still struggled to implement it using the Golang Struct and Maps. One of the obstacles I had was because after unmarshalling the json data, the output was in a Golang interface type, which was not iterable like say a slice. A Golang slice is the equivalent  of a python array. Therefore, to overcome that barrier, I created an empty slice ...
Read more