How OpsGenie help me and Why I returned to the pdf long Incident report?

-

 Hi!


First of all, I would like to say a big thank you for the OpsGenie team for each integration (Slack, call routings, apps, Jira, etc.). Because that integration helps me to reduce the time of reaction to the incident.
So, let's start step by step:
We are using OpsGenie since the end of 2016. On that period OpsGenie had a smooth option for delivery SMS notification for our Nagios in the critical problem. Also, it was additional pros as an escalation workflow. Based on flow which is described on official docs we go forward.

undefined

Source: https://docs.opsgenie.com/docs/alert-notifications-flow

Now our scheme a little bit complicated and more integrated with another part of the infrastructure.

My one of the purpose was autogenerating of the incident report, which was required in our company. Why did I want to have autogenerated? Because we had a pdf template that includes around 50 questions.

Снимок экрана 2019-12-01 в 01.27.15.png

As a result, I hate the process of fill info into that report and every time as post mortem I thought what I need to do for improving availability. As an example If I reduce the number of the incident I will not fill that report, hence no incident - no report.  

image.png

 

Once we had all things as automatic, I just click and put everything into Jira and forgot about follow up incident report and additional investigations.

As an example, after the last incident, I did not think about improves, which is so bad. Now I especially open the old template with many questions and fill just for fun. As result during the answer to questions for Incident report I hate again and start to think what I need to improve to sleep better :)

Conclusion: 

Sometimes we need to balance automatic things and manual, in my use case I returned to the manual process. Because in my view if we should have so specific manual report which motivates you to improve the root cause process issue. :) 

What do you think? If you have other opinions feel free to write here, please.

As bonus you can use that interesting book which really include a lot of aspects of incident and accident reporting. http://www.dcs.gla.ac.uk/~johnson/book/C_Johnson_Accident_Book.pdf  

https://www.opsgenie.com/webinars/best-practices-for-incident-management

 

 

Cheers,

Gonchik Tsymzhitov

Comments

Post a Comment

Popular posts from this blog

Overview and practical use cases with open source tracing tool for Java Apps. Glowroot. Installation

-
Image
In that small article, you can find how to install the agent of Glowroot. Installation of the application is quite simple on agents, and this article shows a scheme for working with a built-in collector, but for industrial installations we use it with a bundle with elasticsearch. The installation can be both for individual nodes and so for the central collector. In this case, consider for a separate node. Prerequisites: {jira_home} - is location of Jira home directory. {jira_installation_directory} is the location of Jira installation directory.   Steps: Downloading the installer wget -c https://github.com/glowroot/glowroot/releases/download/v0.13.6/glowroot-0.13.6-dist.zip To check, create a directory via command   mkdir -p /{jira_home}/glowroot/tmp Let the Jira process write and set ownership for simplicity, but it is recommended that you just give the write ability to the owner of the Jira process. chown -R jira: /{jira_home}/glowroot We additionally set the argument to setenv.sh in
Read more

Atlassian Community, let's collaborate and provide stats to vendors about our SQL index usage

-
  Hi!  Gonchik is in touch. Today I would like to get a little bit of help from you related SQL indexes on your Jira installation (Data Center, Server edition does not matter).    I would like to share a story about  PostgreSQL  and  Jira 8.13.3  ( JSD 4.13.3 )  release.  In that post I will be happy if you answer and comment about your instance indexes, as those info can help to improve the existing situation of heavy indexes.  Typically, it starts from improvement of configuration (e.g. using  https://postgresqltuner.pl/ ),  then query analyzing, adding indexes, after removing as heavy one (shortly  https://wiki.postgresql.org/wiki/Index_Maintenance ) :)    I use like this query in PostgreSQL: SELECT s.schemaname,        s.relname AS tablename,        s.indexrelname AS indexname,        pg_size_pretty(pg_relation_size(s.indexrelid::regclass)) AS index_size,        idx_tup_read,         idx_tup_fetch,         idx_scan FROM pg_catalog.pg_stat_user_indexes s JOIN pg_catalog.pg_index i O
Read more

How only 2 parameters of PostgreSQL reduced anomaly of Jira Data Center nodes

-
Image
  Hello community, Gonchik Tsymzhitov is in touch. Today, I would like to share with you a short story about postgresqltuner.pl in usage.  So from previous articles I hope you configured the PostgreSQL server and postgresqltuner.pl.  After executing command, ./postgresqltuner.pl --ssd for ssd disks server. You can see like this output: postgresqltuner.pl version 1.0.1 [OK]      I can invoke executables Connecting to /var/run/postgresql:5432 database template1 as user 'postgres'... [OK]      The user account used by me for reporting has superuser rights on this PostgreSQL instance =====  OS information  ===== [INFO]    OS: linux Version: 5.4.17-2036.102.0.2.el8uek.x86_64 Arch: x86_64-linux-thread-multi [INFO]    OS total memory: 41.03 GB [OK]      vm.overcommit_memory is adequate: no memory overcommitment [INFO]    Running under a vmware hypervisor [INFO]    Currently used I/O scheduler(s): mq-deadline =====  General instance informations  ===== -----  PostgreSQL version  -----
Read more