LogoLogo
Ops IntelligenceAsset IntelligenceObservabilityRobotic Data
  • Introduction
  • How it Works
  • Getting Started
  • Glossary
  • Implementer Guide
    • cfxDimensions Installation
      • Hardware and Software
      • cfxDimenions on VMware vSphere
        • Post cfxDimensions VM Installation
      • SSL Certificates Installation
      • cfxDimensions Setup & Install
        • Known Issues
      • cfxDimensions High Availability
        • GlusterFS Operations
        • Minio Operations
        • MariaDB Operations
      • cfxDimensions Start, Stop order
      • Macaw CLI
        • macaw CLI Installation
          • macaw CLI v2.1.17
        • macaw setup
        • macaw infra
        • macaw platform
        • macaw user
        • macaw application
        • macaw status
        • macaw services
        • macaw clambda
        • macaw techsupport
        • macaw backup
        • macaw restore
        • macaw reset
      • Release Notes
        • cfxDimensions v2.0.3
        • cfxDimensions v2.1.17
        • cfxDimensions v2.2.20
    • cfxDimensions Backup & Restore
    • cfxOIA Installation
    • cfxOIA Application Services
    • cfxOIA Release Notes
      • cfxOIA v5.1.5
      • cfxOIA v5.1.5.2
      • cfxOIA v5.1.5.3
      • cfxOIA v6.0.0
      • cfxOIA v6.1.0
  • KEY FEATURES GUIDE
    • Incident Management
      • Incidents Overview
      • Create Incident
      • Incident States
      • Accessing Incident
        • Stack
        • Alerts
        • Metrics & Logs
        • Insights
        • Collaboration
        • Diagnostics
        • Remediation
        • Attachments
        • Activities
      • Incident Actions
    • Alert Management
      • Alerts Overview
      • Alert Analytics
      • Alert States
      • Alert Sources
    • Advanced Alert Configuration
      • Alert Mappings
      • Alert Enrichment
      • Alert Correlation & Suppression
        • Creating and Updating Correlation Policies
        • Creating and Updating Suppression Policies
        • Correlation Recommendations
    • ML Driven Operations
    • Data Exploration
    • RDA (Robotic Data Automation)
      • Accessing UI
      • Sources Addition and Configuration
      • Check Connectivity
      • Proxy Settings
      • Explore
        • Bots
        • Pipelines
        • Schedules
        • Jobs
    • Analytics
  • UI & PORTAL FEATURES GUIDE
    • Filters Management
    • Customizing Table Views
    • Exporting Data
  • Administrator Guide
    • User Roles & RBAC
    • Collaboration
    • Projects
      • How to add Project
      • Configure Project
        • Stacks
        • Incidents
        • Alerts
        • Messages
          • Message Endpoints
            • Rest Data Consumer
            • Kafka Message Consumer
            • ServiceNow SaaS
            • Webhook with Basic Authentication
          • Message Mappings
        • Teams
        • Datasources
        • Resolution Codes
  • INTEGRATIONS GUIDE
    • Integrations Overview
    • Featured Integrations
      • AppDynamics
      • Dynatrace
      • Microsoft Teams
      • NetApp Cluster Mode
      • NetApp 7 Mode
      • Prometheus
      • ServiceNow
      • Slack
      • Splunk Enterprise
      • VMware vCenter
      • Zabbix
      • NodePing
      • Nagios XI
      • Check MK
      • VMware vRealize Operations
      • PRTG Network Monitor
      • Grafana
      • AWS Cloudwatch
      • ManageEngine OpManager
      • PagerDuty
Powered by GitBook
On this page
  1. Administrator Guide
  2. Projects

How to add Project

PreviousProjectsNextConfigure Project

Last updated 4 years ago

How To Create a Project

Login as Project Administrator and select OIA (Ops Intelligence & Analytics) application. The Projects view is displayed. Click on 'Add Project'.

Enter the project details.

Add Project

From above ‘Add Project’:

  1. Enter Name for the Project

  2. Enter Project Description

  3. Enter Fully Qualified Domain Name (FQDN)

  4. Enter the number of incidents that could be created within the time period. For example in the above figure, 3 incidents to be created for 5 Minutes. This is to avoid unnecessary load on the system. If more incidents are created then they will go into the ‘Throtting’ stage. The incidents that are moved to Throttling needs to be manually processed by the user.

  5. Enter the number of Minutes, Hours or Day for the time period within which the above mentioned number of incidents can automatically run and fetch the data. An example is to create 3 incidents within 5 Minutes and the user enters 5 in this field.

  6. Select MINUTE, HOUR or Day and this combined with the above field will define the time period. For above example, the user selects MINUTE

  7. Throttle Incident after (time in minutes) - Enter the number of minutes a job can run before it is moved to throttled stage. As an example, if a job takes more than 15 minutes in pulling the information and to avoid any performance bottlenecks, the user can enter 15 in this field. Within 15 minutes, the job is not completed, then the job is moved to the throttled stage and can be completed later (when there is no other load on the system).

Click ‘Next’.

  1. In the next view, it will collect incident purge settings so that unused incidents are archived after a certain time (in days). The view is as displayed below.

Auto archive incident in days - after the entered days, the incident is moved to archive and can be accessed from incident archive.

  1. Auto delete incident data in days - after the entered days, the incident data is automatically deleted

  2. Auto delete incident - after the entered days (say in 365 days), the incident is automatically deleted.

Click ‘Next’. In this view, select all the data sources applicable to the project and click on ‘Finish’.

Once the project is created, it will be in an inactive stage and will move to the Active stage once background processing is completed.

Once the project is in ‘Active’ mode, the user can click ‘open’ displayed on the project to navigate into the project.

Create Project - Purge Settings
Add Project - Select DataSource

Once Project is created, it needs configuration before users can start working on Alerts and Incidents. Click .

here