cfxOIA Application Service Name
Email service is used to export and share the reports or dashboards with users through email.
Scheduler service is used to schedule different types of jobs, some of them are ML training, CMDB / Inventory data updates, and internal application jobs.
cLambda is a serverless function service that is used for on-demand job execution.
Dataset manager service is to provide management function to deal with datasets for reporting and analytics (Deprecated)
It is used to export the reports shown in the UI. Some of the example reports are Alerts / Incidents data.
It is used as a secure password store which consists of credentials for different data sources/endpoints. Other application services query safebox service for respective credentials during runtime on-demand
It is used for workflow lifecycle management and supports calling different types of automated workflows for running ML experiments, incidents data generation, and other data collection.
It is used as a caching service for current alerts (up to 3 days, with 60 seconds refresh rate) in a data frame and provides faster data access to the reports within the Alert management UI
It is used as a caching service for all alerts (current & historical, with 60 minutes refresh rate) in a data frame and provides faster data access to the reports within the Alert management UI
This service is primarily used to maintain the metadata/identity of MSP & Customer/Organization level information.
This service is used to load all of the necessary Minio buckets during the initial start-up. These Minio buckets will be used by different services like alert ingester, CaaS, cfxdx, and other services.
This service is to load all of the UI reports like Application icons, Projects, and dashboard after the user's login.
It is used to impose RBAC based user roles & permissions
It is used to manage internal application notifications from various application services and pop them up in UI as notification events.
It is used to provide user management and roles and it works with app-access-manager service
It is used to provide a user interface in UI to store/upload and query/download the data files. It uses Minio object storage in the back-end to store all of the data files. Additionally, it is used by other application services.
This service is used to load all of the configuration pages in UI like Alerts/Incidents/cfxdx sources etc.. an example, configuration operations like create/update/delete webhooks for incoming alerts/incident updates and other operations under Project's configuration.
It is used to load all of the reports in the UI
This service is used to build new reports pages or update existing analytical reports based on the user's requirement
It is used to provide a data source integration feature to add/edit/delete for different data source connectors (Deprecated, it will be removed in future releases)
This service provides incident lifecycle management, like open, update, and close incidents automatically after alerts are processed successfully.
This service is used to configure and integrate different collaboration technologies likes Microsoft teams, ServiceNow, Slack & Pagerduty, etc.
This service provides back-end support to Datasources services while integrating with external data sources like ServiceNow, VMware vROps, VMware vCenter, Microsoft Teams, and Pagerduty (Deprecated, it will be removed in future releases)
This service process persists alerts and their state transitions. It manages the lifecycle of alert policies. It correlates/suppresses alerts based on the defined policies. It also forwards the active alerts for incident creation. Alerts are consumed via notification from the alert ingester service.
It processes incoming events/alerts from external sources. alerts/events are first mapped into a concrete event - alert/incident/message. Once the mapping is complete, the alerts/events are classified using an ML clustering algorithm (if applicable) and enriched by processing them through an enrichment pipeline comprising a sequence of enrichment steps. The enriched alerts/events are then published for further processing by the alert-processor service
This service is used to listen to or poll events from an external source on-demand / runtime or by schedule. Some of the example events are alerts/incidents/messages from an external source into the cfxOIA system for further processing.
This service manages all of the Machine Learning (ML) lifecycle management operations like create, update, execute, activate, delete experiments, etc(for Alert/Incident Clustering and Regression).
This service discovers unique asset information based on refresh interval by asset IP address from alerts table.
This service is used to ingest alerts from different monitoring tools which send email-based alert notifications.
This service is used to ingest alerts from different monitoring tools which send alert notifications over HTTP(s) protocol (Webhook) using POST or PUT operations.
This service is used to integrate with many external data sources like ServiceNow, VMware vROps, VMware vCenter, Nagios, PRTG, Splunk, Elasticsearch, etc to query the inventory, logs, metrics data, transform them using native data management pipelines and consume them for Alert / Incident data enrichment for correlation, noise reduction and for probable root cause recommendations
This service is used to launch the streaming micro-services on demand and execute streaming jobs for incidents
This service is used to track all incoming alerts/events into the cfxOIA system and report their state transition status throughout their lifecycle.