cancel
Showing results for 
Search instead for 
Did you mean: 
intapiuser
Community Team Member
Community Team Member
This article is a reference point for understanding Sisense services and what their purposes are.
The notes column contains supplemental information about the service. Please note that this is not an exhaustive list of how you would interact with the services for each scenario.

Current List of Sisense Services (as of Version 7.2)

Service Name
Name
Purpose
Notes
 
 
 
 
 Sisense.Broker
Broker
Responsible for communication between services. All micro-services utilize the Broker service.
In High Availability deployments, this service is associated with RabbitMQ as well.
Ensure this service is running as it is a prerequisite for other Sisense services to function.
 Sisense.CLRConnectorsContainer 
CLR Connectors
Responsible for powering CLR (.NET) connectors.
You may restart this service if you're having trouble with particular CLR-based connectors.
 Sisense.Collector
Collector - Sisense Internal Monitoring
Responsible for internal monitoring and collection of data about the machine and process performance.
This service must be running in order to send logs for Sisense monitoring.
 Sisense.Configuration
Configuration Manager
Responsible for powering the Configuration Manager application located at http://localhost:3030 on your Sisense webserver.
Also exposes APIs for other configurations.
You may restart this service if you find you're having trouble getting the Configuration Manager site to load.
 Sisense.Discovery
Discovery
Responsible for saving and storing configuration changes including those made in the Configuration Manager.
Typically you will leave this service alone outside of a Sisense migration.
 Sisense.ECMLogs
ElastiCube Manager Logging
Responsible for storing build logs from ECM 1.0 and ECM 2.0, PSM, APIS, etc.
There should not be any reason for starting this service outside of basic configuration changes (Sisense migration, MongoDB changes, etc).
 Sisense.ECMS
ECM 1.0 (Desktop ElastiCube Manager)
Responsible for powering the Desktop ECM.
You may restart this service if you're seeing issues building or accessing ElastiCubes on the desktop.
 Sisense.ECMServer
ECM 2.0 (Web ElastiCube Manager)
Responsible for powering the Web ECM.
You may restart this service if you're seeing issues building or accessing ElastiCubes within Sisense Web.
 Sisense.Galaxy
Galaxy
Controls the majority of web server logic.
At this time this service also controls:
  • Emails
  • Reporting
  • Export to image
You may choose to restart this service in the following example cases:
  • Many API calls that failed with "api not found".
  • User can log in but not able to navigate through dashboards upon login.
  • Emails are not going out.
 Sisense.Gateway
Gateway
Main entry point of the Sisense system.
This service routes the API between many of the microservices.
By default, this services listens on port 8081 and can be changed within the Configuration Manager.
You may restart this service if you are having trouble reaching the Sisense site on your designated port.
 Sisense.HouseKeeper
HouseKeeper
This service is responsible for memory management of the Sisense application.
Typically there is not a need to restart or modify this service.
 Sisense.Identity
Identity
Responsible for Sisense groups, roles, users, etc.
This service is responsible for authentication and user management.
You may restart this service in instances where your user is unable to log in due to errors in authentication (not related to SSO authentication).
 Sisense.Jobs
Jobs
Responsible for triggering jobs including emails after a cube build, emailed reports on a schedule, etc.
Typically there is not a need to restart or modify this service outside of troubleshooting scheduled jobs.
 Sisense.JVMConnectorsContainer
JVM Connectors
Responsible for powering JVM connectors.
You may restart this service if you're having trouble with particular JVM-based connectors.
 Sisense.Orchestrator
Orchestration
Utilized in HA to synchronize and distribute built ElastiCubes on the build node to the query nodes.
You may restart this service changing HA configuration settings. Please consult the HA documentation before restarting this service.
 Sisense.Oxygen
Oxygen (Licensing)
Responsible for communicating with Sisense to verify licensing
You may need to restart this server if you are having licensing issues within the ECM or Sisense Web.
Must be restarted upon license update (along with a logout and log back in).
 Sisense.Plugins
Plugins Management
Node.js service which builds plugins.
Users do not need to restart this service each time they change plugins.
Plugins service watches the plugins folder for changes and runs a build mechanism automatically.
 Sisense.QueryProxy
Query Services
Provides a unified way to translate and access the backend SQL Engines.
Responsible for query executions, throttling, load balancing, versioning, streaming and results formatting.
This service must be running in order for query execution to work.
 Sisense.Repository
Repository
Responsible for storing Sisense metadata including:
  • Dashboards
  • Users
  • Data security
This service maintains connection to the files contained in MongoDB
This service must be running in order for users to view dashboards and log into Sisense Web.
 Sisense.Shipper
Shipper
Responsible for shipping logs to Sisense for monitoring. 
Reads data from C:\ProgramData\Sisense\Monitoring\LOGS folder and ships it.
This service must be running in order to send logs for Sisense monitoring.
 Sisense.SPE
Data Prep and Streaming Engine
Responsible for powering:
  • Export to Excel
  • Preview table
  • Data Wizard
  • Custom tables and custom columns
You should restart this service when changing configuration settings for any of the modules power by it.
 Sisense.StorageManager
Storage Manager
Responsible for storing files for file-based connectors such as CSV and Excel files
Typically no need to restart or change this service.
You should restart this service when changing configuration for this component such as changing the max file size or minimum hard disk space for uploading files..
 Sisense.Usage
Usage Service
This service is responsible for saving off Sisense usage data.
Typically no need to restart or change this service.
You may restart this service after a change in configuration of the Usage feature.

Notable services on Sisense Version 7.1 and below:

Service Name Name Purpose Notes
       
 ElasticubeManagmentService ElastiCube Management

Responsible for powering the Desktop ECM.

This service was replaced by Sisense.ECMS and Sisense.ECMServer.

You may restart this service if you're seeing issues building or accessing ElastiCubes on the desktop.
 Sisense.ECMLogsPersistenceService  ECM Logs

Responsible for storing build logs from the Desktop ECM.

This service was replaced by Sisense.ECMLogs.

There should not be any reason for starting this service outside of basic configuration changes (Sisense migration, MongoDB changes, etc).
 Sisense.Pulse Pulse

Responsible for powering pulse alerts.

This service was replaced by Sisense.Broker.

You may restart this service if you are experiencing issues with Pulse across the board.
Rate this article:
Version history
Last update:
‎02-13-2024 01:25 PM
Updated by: