WIP - Defining Personas and Use Cases for Enhanced OBS Cluster Utilization

[schwesig]

fixes partly nerc-project/operations#443

• Exploration of Additional Personas for Observability Cluster Based on Retention Rate Requirements nerc-project/operations#461

Defining Personas and Use Cases for Enhanced OBS Cluster Utilization

Motivation

Establishing the new Observability (OBS) cluster, it's important to ensure that it fits and answers the diverse needs of our stakeholders/users.
A one-size-fits-all approach to metrics, logs, traces, retention policies, dashboards, outputs, triggers, actions, and even more may not adequately address the unique requirements of each user group.
To optimize the output and efficiency, as the acceptance/usability of the OBS cluster, a structured approach to identifying and tailoring these elements to specific user personas and use cases is important.

Objective

Develop a framework of personas and use cases. This framework will guide the customization of observability tools and processes to meet the diverse needs; ensuring relevance, usability, and effectiveness.
One goal is to create a matrix that categorizes observability features and settings to each persona's needs/wishes.
Making it possible to reduce redundancy, and hopefully helps to create modular and easy customizable outputs.

Completion Criteria

• A matrix that clearly defines how each persona interacts with the OBS cluster, including triggers, urgency, customization needs, and preferred methods of interaction (e.g., alerts, dashboards, reports).
• Observability solutions for each identified persona, ensuring that their unique needs are addressed effectively.

Description

To enhance the acceptance of our new OBS cluster, we must tailor its capabilities to the specific needs of various users and needs.
This involves understanding the tasks, challenges, and objectives of each group, allowing us to design a more intuitive and useful observability experience.
By establishing use cases and customizing the observability environment accordingly, we can ensure that each user receives relevant, actionable insights in the most efficient, low noise manner possible.

Guidelines

• Low Noise (get rid of distraction, too much alerts)
• Context (a number is only useful set in a context, e.g. compared to/ correlated with)
• Responsibility (an alert is only as useful, as it is clear, who acts on it)

Considerations

• The need for flexibility in the matrix to accommodate evolving needs and new personas.
• The balance between providing detailed customization options and maintaining ease of use and system performance.

Discussions

The matrix and the following table will serve as foundational tools in aligning our OBS cluster's capabilities with the needs of our users:

Persona	Trigger	Outcome	Channel	Urgency	Cluster	Reaction	Retention
Example	Time, Middle of month	Custom Dashboard	Web, Email	Medium, 1day reaction time	prod, rhods	Budget Planning	180 days

This issue calls for collaboration among team members to identify key personas, articulate their unique needs, and translate these into actionable insights and customization strategies.

[schwesig]

idea from todays meeting

• using metrics for top 5 lists like
  • most time on the system
  • best usage of resources
  • late night users, early birds
  • earliest starter
  • most days in a row
  • ...