Categories: All - documentation - communication

by Pierre Crochelet 1 day ago

11

User challenges

Users face numerous challenges with the current system, including difficulty in getting data in and out, complex configuration, and inconsistencies in frameworks. Stability issues are prevalent across various platforms like Vortex, Protegrity, DAW, Airflow, and Kubernetes.

User challenges

User challenges

What problem do you want to solve?

Type in the box.

E.g.

I can't save moneyI can't lose weightMy neighbor is very loudI can't quit smokingI don't exercise enough

Access

Too many different roles
Data(set) Access is slow
SSP request + deployment is slow
Manual data-access for non-BE projects
Missing capability
Analysts have limited access to necessary data
Strict access rules on Edison

Monitoring

Unclear or no error messages, no access to logging
Lack of observability
No dashboards on pipelines statuses, data quality, dataset creations, ...
Lack of alerting
Limited monitoring on the platform
Lack of Airflow job monitoring

Data Governance

Lack of ownership structure
Unclear who to contact
Analysts find it difficult to find the right files
No data catalog

CI/CD

Now it's time to execute your plan.

You can also:



Thanks for Mind Mapping!

Release process slow and unstable
Difficult to test pipelines
No data on DEV & ACC
Slow to setup new pipelines
Lack of automation

Infra

Create a plan of how to solve the problem.

Vortex stability
Protegrity stability
DAW stability
Releases
Kubernetes stability
Lots of small issues adding up
Airflow stability
Fast deployment of many pods

Frameworks

This branch will guide you to think about the possible solutions available to your problem.

Getting data in and out of Edison is difficult
Framework complexity does not align with user's needs
Complex to configure
Inconsistencies between frameworks

Workflows

To solve your problem 'User challenges' you need to establish clear goals of what you want to achieve.

Write down your goals, each goal on a new branch connected to this topic.

Difficult to visualize data quality and lineage
Missing tool to analyze lineage and quality json files
Interruption due to re-login
No user-based login / portal
Difficult to analyze a pipeline
Missing Airflow Features
Missing non-file-based ingestion capabilities
Difficult to navigate files in DAW
Missing capability
Unable to share notebooks from DAW
Unfamiliar with Git
Technical knowledge required to use DAW

What are your goals by solving this problem?

Unfamiliar with Python/Git

What potential opportunities lay hidden in this problem?

Think of something positive caused by this problem.

Communication & documentation

To understand your problem this branch will guide you to:

Describe your problem in detail

Press the next below to continue.

Difficult to configure frameworks
Difficult to test ingestion process
Missing/Unclear documentation
Slow setup of ingestion process
Unclear documentation
Slow to setup new projects

What is the cause of this problem?

Difficult to problem solve / debug
Difficult onboarding for analysts

Describe the ideal situation if this problem didn't exist.

Missing, Unclear documentation
Lack of alerting

What do others, who are not involved think about this problem?

Limited communication of issues to users

What actions will you take?

Unable to share notebooks from DAW
Compliance issue notebooks can contain data
Unable to share files from DAW

Describe the current situation of the problem.

What is happening now?

Type your answer in the box.

Compliance issue