0% found this document useful (0 votes)
6 views6 pages

Project Optima Description

Uploaded by

sahibgorwal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views6 pages

Project Optima Description

Uploaded by

sahibgorwal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

PROJECT OPTIMA DESCRIPTION

Project Description---->

OPTIMA

It is a network performance monitoring tool based on ETL process

On daily basis we receive data from vendors the data is comming to BI team. BI team
crates the date wise folder for the data.At BI team server my user is already created so
we just pull the data threw SCP. we get the data from BI team in every 5 min this can
be done by scheduling the job in crontab.

At ETL server we have created a Data folder basically we created date wise
folder(/app/data/scp/28012019/) in which data is stored that comes from BI
team.There is a predefined script which takes the data and parse(transform) them After
the data is parse it stored in the Parse folder which is also created at the ETL server
and then Successfull parse data is stored in the load folder.we take data from the load
folder and load them into database (In tabular form).

At the same time during parsing and loading Logs are also created at ETL server In
the data folder we created a log file in which we can see the success logs and failed
logs for the extraction the data which is extract successfully is go into the success logs
and if there is any error occur then it goes into the failed logs. And at the same time
we also created a backup file in which we take the backup of all the data that is
successfully fetched from BI team.

Same for the transformation and loading also.

When data is Load into the the database we fetch the data from there and generate
KPI for our customer by which they Analize their business performance. We do all
these

things threw SQL queries.


P1 ticket issue

--->If P1 comes and you are alone in the shift -:

1 -first I will check whether the ticket raised deserves P1 priority or not

2 - I would look for contacting for more experienced guy than me if possible.

3 - Look forward for contacting any of the team leads either of any shift

4 - Try Contact a person of IM PM or CM team

5 -And if in case I am not able to make contact with any of the experience holders
then I look forward for suggestion to my friends who are of profile same as of me

6 - I can look forward to the documents in which this type of issue has happened
before and if it has happened then follow the SOPs and and try to fix the issue.

7 -I can also try convince my client to hold the SLA so that it doesn't gets breach

---->Have you ever work on P1

As we know server to server have password less connectivity once their ssh key is
dropped and our connectivity is lost.we can check it by logs it shows the connectivity

failure. Then we try to check by making connectivity manually but it cannot done
because ssh key drop.then we again sync the key and then entered the new generated
key in the known host file then they allow and connection is build.

ITIL PROCESS:

ITIL stands for information technology infrastructure library which is a set of process
to carry out services.

It helps business to improve service levels and reduce the cost of IT operation.
The goal of ITIL is to make better decision making, enhance efficiency and achieve
high service quality.

Its has many teams like incident management team(IN), problem management(PM),
change management(CM), etc.

IN: incident management

First it checks whether the raised ticket deserves the same priority or not.
if it does not deserve the same priority then it deals with client to change its priority
after giving full explanation.

This teams assigns the relevant team to resolve the ticket as soon as possible so that it
does not breaches the SLA, hence the respective teams start there work
over the ticket raised and IN teams keeps a check over that team and SLA
simultaneously in order to prevent SLA from breaching.

PM: problem management

After resolving the issue over the ticket the role of PM team starts. It asks for the RCA
related to the issue from the respective team or person who worked on it.
after receiving proper RCA the PM team in co-ordination with the team that had
solved the issues look for a change request under a CAB call(change approval board)
and explains everything to the client why they are asking for a change request, Is there
any downtime or not, etc so that the issue doesn't gets triggered again
and again in future.Hence after total discussion, a ticket is then raised in order to
provide permanent fix to that problem.It forms a set of instructions (SOP)
standard operation procedures so that if that particular issue arises again then it can
solve the issue quickly.

CM: change management: The process of changing something in system with


minimum disturbance of running system.

API: API (Application Programming Interface) platform is a suite of tools and


services that facilitate the development, testing, deployment, and management of
APIs. These platforms are essential for building, monitoring, and interacting with
APIs, which are the backbone of modern software development, enabling
communication between different software systems and services

Postman: Postman is one of the most popular API development and testing platforms.
It provides a comprehensive suite of tools that cater to the entire API lifecycle.

Azure: API Management is a fully managed service provided by Microsoft Azure that
allows developers to create, manage, secure, and analyze APIs in a scalable and secure
environment.

@@@@@@@@@ First we talk about the issue at our Application tool end

_____ APPLICATION startup/stop ISSUE

this issue occurs when we statrt up the application for the first time after the downtime
for a change is comming to an end, for this we check the interlocking i.e creating
dependencies for database integration, ip connected with app so that app doesn't start
without all these done by dovelopement team and the other reason could be -if the
allocated memory/ram/discspace is less this can lead to a prb in starting up or down
(check in logs).

___APPLICATION CONNECTIVITY ISSUE

URL= we check the application URl by our test user whether it is working properly or
not.

IP/port= we also ping the the database server ip so that we can check whether the
server,proper port no is connected or not.
SSL certificate= we also check the SSl certificate of our domain url for the security of
the url.

internet=application will not be open if the internet is not working propertly.

__APPLICATION LOGIN ISUUE

the application doesn't accept the perticular user for the following reason = user was
locked,passwd change/expired,inactive etc or limit of login user has exceeded,

so for this kind of issue we ask to client for screenshot of the error,then talk to
application team to resolve this type of issue.

__APPLICATION HANG

application will the hang for many reasons such as if the incomming request on
application has suddenly increased ,so for this first we check the logs and look into

for transaction per second and restrt the application.

__Application Logs issue

if the folder is deleted accidently then no log created ,so for this we also restart the
application.

__APPLICATION FUNCTIONALITY ISSUE

button not working(bug)

reports gets generated but data is not available [ask developer why blank reports are
generated after connection lost]

*pending files are sent on another day and reports of today are generated on data of
previous days.

You might also like