metno / S-ENDA-documentation

Temporary documentation and use case descriptions for the S-ENDA project - when concepts are tested and verified, content is gradually moved to more long term solutions.
https://s-enda-documentation.readthedocs.io/
2 stars 6 forks source link

Define an alert team and set up pagerduty services for this team #302

Closed mortenwh closed 2 years ago

mortenwh commented 2 years ago
charlienegri commented 2 years ago

the teams currently present in pagerduty are here https://metno.pagerduty.com/teams Screenshot from 2022-06-16 19-14-39.png s-enda could be a service part of one of those teams or we can set up a new team perhaps.. idk what's best, I guess this needs to be discussed also with people from IT

charlienegri commented 2 years ago

as we discussed, I can open a ticket requesting the creation of a new data-management team
or we can have "data-management" as a project under PROMO, which is the most cross-disciplinary of the current teams there I guess (but then we all need to be added to that team).
what do you think @mortenwh ?

charlienegri commented 2 years ago

ticket https://hjelp.met.no/tas/public/ssp/content/detail/incident?unid=34236923e7fd4b208c720b4b1f6e8090

charlienegri commented 2 years ago

Screenshot from 2022-06-27 07-48-00.png

the new team has been created, I requested "data-management" as name but they set "S-Enda-data-management"... i guess this can be changed at some point

charlienegri commented 2 years ago

next step is to start defining services for the team, which level of granularity do we want? we could have a general s-enda service covering all the monitoring needs, or we could split services in way more granular categories, like for example MMS, Event Queue, CSW Agent.. or something in between like a service "metadata services". the advantage of granularity is the possibility to assign different people in the team as responders for different services

mortenwh commented 2 years ago

I don't like that they added s-enda. Who made it? I need to talk to them..

On Mon, Jun 27, 2022 at 7:50 AM Charlie Negri @.***> wrote:

[image: Screenshot from 2022-06-27 07-48-00.png] https://camo.githubusercontent.com/f4a292b90044dc6f03b7dc55e94aa9a959916b30b6734bafcdfd60f707bb4d3b/68747470733a2f2f696d616765732e7a656e68756275736572636f6e74656e742e636f6d2f3632613332613633353034623363303961656131363062612f34393035313863382d306530382d343533372d613032642d336363363236353736393064

the new team has been created, I requested "data-management" as name but they set "S-Enda-data-management"... i guess this can be changed at some point

— Reply to this email directly, view it on GitHub https://github.com/metno/S-ENDA-documentation/issues/302#issuecomment-1166899859, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA2UBKUBMXK6IQFBBHQKLTVRE6JDANCNFSM5Y6IGDJA . You are receiving this because you were mentioned.Message ID: @.***>

-- Morten Wergeland Hansen, PhD Senior scientist / Data Manager Meteorologisk Institutt / Norwegian Meteorological Institute T.: (+47) 915 47 844

charlienegri commented 2 years ago

since I have admin rights I went ahead and changed the name Screenshot from 2022-06-27 12-45-09.png

charlienegri commented 2 years ago

alert setup tested, everything seems to be working for now