Change Details

Please grant @debt access to the eventlogging db's and provide a bit of knowledge on how to use them, resources needed, etc. - [ ] **Step 1**: Generate a SSH RSA key pair. See [[ https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/ | this help article on GitHub ]] for instructions. This will create two files in ~/.ssh: a private key (e.g. "id_rsa", which you cannot share with anybody) and a public key (e.g. "id_rsa.pub", the contents of which you will need to share in Step 2) - [ ] **Step 2**: Create a ticket requesting access to stat1002 and stat1003, tagging Ops-Access-Request, and providing the public part of your new SSH key. See T142648 for an example of such a ticket. - [ ] **Step 3**: Once you get access, ask @mpopov to show you how to configure SSH so you can log in. - [ ] **Step 4**: Ask @chelsyx or @mpopov to show you how to get into event logging DB and give you a quick tour, what revision numbers mean, how to look up schema specifications, etc. - [ ] **Step 5a**: Start learning SQL. ([[ http://sqlzoo.net/ | SQLZOO ]] has a nice tutorial system where you learn by actually running SQL queries right there on the website.) - [ ] **Step 5b**: Ask @chelsyx or @mpopov for some example queries.

Please grant @debt access to the eventlogging db's and provide a bit of knowledge on how to use them, resources needed, etc. - [X] **Step 1**: Generate a SSH RSA key pair. See [[ https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/ | this help article on GitHub ]] for instructions. This will create two files in ~/.ssh: a private key (e.g. "id_rsa", which you cannot share with anybody) and a public key (e.g. "id_rsa.pub", the contents of which you will need to share in Step 2) - [X] **Step 2**: Create a ticket requesting access to stat1002 and stat1003, tagging Ops-Access-Request, and providing the public part of your new SSH key. See T142648 for an example of such a ticket. - [ ] **Step 3**: Once you get access, ask @mpopov to show you how to configure SSH so you can log in. - [ ] **Step 4**: Ask @chelsyx or @mpopov to show you how to get into event logging DB and give you a quick tour, what revision numbers mean, how to look up schema specifications, etc. - [ ] **Step 5a**: Start learning SQL. ([[ http://sqlzoo.net/ | SQLZOO ]] has a nice tutorial system where you learn by actually running SQL queries right there on the website.) - [ ] **Step 5b**: Ask @chelsyx or @mpopov for some example queries.

Please grant @debt access to the eventlogging db's and provide a bit of knowledge on how to use them, resources needed, etc. - [ - [X] **Step 1**: Generate a SSH RSA key pair. See [[ https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/ | this help article on GitHub ]] for instructions. This will create two files in ~/.ssh: a private key (e.g. "id_rsa", which you cannot share with anybody) and a public key (e.g. "id_rsa.pub", the contents of which you will need to share in Step 2) - [ - [X] **Step 2**: Create a ticket requesting access to stat1002 and stat1003, tagging Ops-Access-Request, and providing the public part of your new SSH key. See T142648 for an example of such a ticket. - [ ] **Step 3**: Once you get access, ask @mpopov to show you how to configure SSH so you can log in. - [ ] **Step 4**: Ask @chelsyx or @mpopov to show you how to get into event logging DB and give you a quick tour, what revision numbers mean, how to look up schema specifications, etc. - [ ] **Step 5a**: Start learning SQL. ([[ http://sqlzoo.net/ | SQLZOO ]] has a nice tutorial system where you learn by actually running SQL queries right there on the website.) - [ ] **Step 5b**: Ask @chelsyx or @mpopov for some example queries.