Admin Setup


Available in: Ultimate and Enterprise editions
Available for an additional cost in: Team edition

Get in touch with Sales for licensing questions.

Kibana is an open source workbench that allows for the visualization of data previously indexed in the Memsource analytics warehouse. 

Note: Kibana version 4.1.6 is required to process data from Memsource. Download from the Elastic website.


Memsource steps:

  1. From the Setup page, click Kibana under Analytics and Reporting.
    The Kibana setup page opens.
  2. Click Setup Kibana Access.
    A unique URL is generated that required to visualize data with Kibana.

Kibana steps:

  1. Open the kibana.yml configuration file from Kibana config subfolder. 
  2. Replace elasticsearch_url value (usually "http://localhost:9200") with the URL generated in the Memsource steps.
  3. Ensure the kibana_index value is set to .kibana
  4. Save the kibana.yml file.
  5. Start Kibana from the the Kibana bin subdirectory.
    • Windows: double-click kibana.bat
    • Other O/S: double-click kibana (other users).
  6. Verify setup.
    The following is visible in the command prompt window:

    Note: Command prompt window must stay open to maintain connection to Kibana.
  7. Enter localhost:5601 into the address bar of a browser to access the visualization workbench.

Configuring Kibana

  1. Index patterns are required for visualization and are applied in Settings under the Indices menu.
    The following index patterns are currently available:
    • (job.dateCreated)
    • (jobPart.dateCreated)
    • (jobPart.dateCreated)
    • (jobPart.dateCreated)
    • (
    • (lqa.dateCreated)
  2. When creating indexes, the expression in brackets represent the recommended Time-field name for the given index. Any or all of the indexes available can be configured.
  3. Once the indexes are registered, data can be visualized through the Visualize tab.

Index Classifications

  • Job index
    • Contains information about job sizes (words, pages etc.), who created the jobs, when they were created, filetypes, projects, and organizations they belong to.
  • Job Part index
    • Jobs themselves do not have statuses or assigned users. This type of information is stored in terms of job parts (i.e. jobs in different workflow steps constitute different job parts). Otherwise, the same of data as in the Job index are available (filetype, project, organization etc.).
  • Analysis index
    • Information about Analyzed Job Parts (divided into match categories) with and without Net Rate applied.
  • Costs index
    • Costs for the Job Part (based on Price Lists).
  • API index
    • Summary of API usage.
  • LQA index
    • Breakdown of LQA evaluations entered for Job Parts based on defined categories, subcategories and severity.


A selection of configuration samples.