Skip to content

dataiku/dss-plugin-dataiku-pulse

Repository files navigation

Dataiku PULSE Dashboard and Collector

  • Version - 2.1.4

Scope

This dashboard is designed to give Dataiku Admins insights into the DSS instance.

  • Dataiku Insights (API Dataiku)
  • Dataiku Usage (Audit Logs)

Tested Dataiku Versions

  1. v2.1/0
    1. v14.2
  2. V1.X
    1. v14.1
    2. v14.0
    3. v13.5

Installation Notes

Due to the web application being built on Streamlit, installation requires a bit of dedicated code use. Hoping this changes in later DSS versions.

  1. Plugin
    1. Login as an Administrative account
    2. Migrate to Waffle::Plugins and install from GIT: https://github.com/dataiku/dss-plugin-dataiku-pulse.git
    3. Build the code-environment, no containers needed
    4. After the plugin is installed, switch to the plugin settings page and fill in the information ("EXAMPLE BELOW")
      1. PULSE Dashbaord: This is the main parameter set to house all the base configurations for the application. Create a single PARAM_SET named primary (LOWERCASE!) and populate each field.
        1. GitHub Repository Information
          1. Repo: https://github.com/dataiku/dss-plugin-dataiku-pulse.git
          2. Branch: main
        2. Dashboard Information
          1. Dashboard Project Key: DATAIKU_PULSE_DASHBOARD
          2. Dashboard Host URL: Hostname or IP:Port
          3. Dashboard Host API: Admin Level Api Key
          4. BLOB Folder: <Dataiku Connection String name [AWS|Azure|GCS]
        3. Worker Nodes
          1. Worker Node Project Key: DATAIKU_PULSE_WORKER
          2. Fill out each host including the local host if you want to track the local host.
            1. Need both Hostname or IP:Port and Admin level API Key
            2. For more custom control add a PARAM_SET name specific to the host for the next section
          3. User: User to own/run the scenarios
          4. Ignore Certs: Auto trust https between nodes
          5. Project Data Parallel: Gather Project metadata in parallel
          6. Cores: How many cores to run for project data
      2. (OPTIONAL) Worker Nodes: This will container additional auto information or custom information per host
        1. Create a PARAM_SET matching the name of the worker node PARAM_SET from the previous section
        2. Custom User, Certs, Parallel/Cores
        3. Macro Configuration: PLACE HOLDER -- Coming v2.2
  2. Code Studios
    1. Create the template name dataiku_pulse_dashboard # this name is important
    2. Setup K8s to run on
    3. Add the Dataiku Pulse (Streamlit Custom) block
    4. Disable permissions for users
    5. Build
  3. Create the Dataiku PULSE Dashboard project based off 1.4.2 information
    1. Go to Macros
    2. Filter on Dataiku Pulse: Initialize
    3. Run Initialize Dashboard
    4. Run Initialize Workers
    5. Switch to Code Studios page under the Code tab
      1. Click the checkbox and publish as a Web Application (No API for this)
      2. Start the Web Application (Auto-Start)
      3. Nothing may be available at first while the first day cycle needs to run to gather data

Data Flow Diagrams

Data Flow Diagram

Contributors

  • Author - Stephen Mazzei
  • Email - Stephen.Mazzei@dataiku.com
  • Special Thanks
    • Development
      • Jordan Burke
      • Ben Bourgeois
      • Jonathan Sill
    • Documentation
      • Rob Harris
    • Project Management
      • Arjun Srivatsa

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages