Memsource users are able to visualize data from their accounts through Kibana, an open-source data visualization workbench. Kibana allows you to visualize and explore all data indexed by our analytics data warehouse, and there is an almost endless number of queries that can be visualized using Kibana.
Kibana version 4.1.11 is required to process data from Memsource.
Data Types That Can be Visualized
All visualizations created in Kibana can also be turned into CSV based tables containing the hard data behind.
Some examples of data indexed through Kibana:
-
Project
Project creation date, last modification, created by, last modified by, source language, target languages, project settings, client, domain, subdomain, business unit, project status, due date, etc.
-
Jobs
Job creation date, last modification, created by, last modified by, source language, target language, assigned to linguist/vendor, due date, workflow step, file type, etc.
-
Analyses
Total wordcount, net wordcount, translation memory matches, machine translation matches, etc.
-
Costs
Costs per project, project margin, etc. (based on Price Lists).
-
API
Summary of API usage, list and breakdown of API calls per period of time, etc.
-
Time Tracking
Collection of time-tracking stats (in ms) follows these principles and can be seen in both MXLIFF files and in Kibana:
-
User clicks into segment #1:
-
Counting of segment #1 thinking time starts
-
Counting of segment #1 editing time starts
-
-
User starts editing segment #1:
-
Counting of segment #1 thinking time is stopped
-
Counting of segment #1 editing time continues
-
-
User clicks into segment #2:
-
Counting of segment #1 editing time is stopped
-
-
When a user re-enters segment #1, the counting starts again and the new times are added to the previous values. If edited upon re-entering, both times are updated. If there is no editing, times are not updated.
-
The thinking and/or editing times are measured for each workflow step separately.
To reach time tracking, use the
com.memsource.web.analytics.data.jobpart
index in fieldsdata.editing.*
.You may need to refresh the jobpart index in the Kibana settings page for Kibana to learn of the existence of these new fields. -
-
From the Settings
page, scroll down to the section and click on Kibana.
The
page opens. -
Copy the unique
.
-
Open the kibana.yml configuration file from Kibana config subfolder.
-
Replace elasticsearch_url value (usually http://localhost:9200) with the URL generated in the Memsource steps.
-
Ensure the kibana_index value is set to .kibana
-
Save the kibana.yml file.
-
Start Kibana from the the Kibana bin subdirectory.
-
Windows: double-click kibana.bat
-
Other O/S: double-click kibana (other users).
-
-
Verify setup.
The following is visible in the command prompt window:
-
Enter localhost:5601 into the address bar of a browser to access the visualization workbench.
Important
The command prompt window must stay open to maintain the connection to Kibana.
Index patterns are required for visualization and are applied in Settings under the Indices menu. The following index patterns are currently available:
-
com.memsource.web.analytics.data.job (job.dateCreated)
-
com.memsource.web.analytics.data.jobpart (jobPart.dateCreated)
-
com.memsource.web.analytics.data.analysis (jobPart.dateCreated)
-
com.memsource.web.analytics.data.costs (jobPart.dateCreated)
-
com.memsource.web.analytics.data.lqa (lqa.dateCreated)
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.
Once the indexes are registered, data can be visualized through the Visualize tab.
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.
These examples use a Vertical Bar Chart, which is the most versatile type of graph Kibana offers. The examples include an Index specification (which index should be chosen). If no results appear, ensure the selected time period is correct.
Most Translated Language Pairs

Configuration:
-
Index
analytics.data.job
-
Metrics
Sum of data.volume.words
-
Buckets
X-Axis - Terms - job.languagePair

Most Expensive Projects

Configuration:
-
Index
analytics.data.costs
-
Metrics
Sum of data.total
-
Buckets
X-Axis - Terms - project.id

Costs Per Linguist

Configuration:
-
Index
analytics.data.costs
-
Metrics
Sum of data total
-
Buckets
X-Axis - Terms - jobPart.assignedTo.linguist.fullName.untouched
-
Filter
quote.tags:"com.memsource.costs.jobPart.raw"
Creates a chart without NetRate applied.
-
Filter
quote.tags:"com.memsource.costs.jobPart"
Creates a chart with NetRate applied.

Costs Per Vendor

Configuration:
-
Index
analytics.data.costs
-
Metrics
Sum of data total
-
Buckets
X-Axis - Terms - jobPart.assignedTo.vendor.token
-
Filter
quote.tags:"com.memsource.costs.jobPart.raw"
Creates a chart without NetRate applied.
-
Filter
quote.tags:"com.memsource.costs.jobPart"
Creates a chart with NetRate applied.

Expected Wordcount vs. Net Number of Words

Configuration:
-
Index
analytics.data.analysis
-
Metrics
Sum of data.total.words
-
Buckets
X-Axis - Terms - jobPart.assignedTo.linguist.fullName.untouched
-
Split bars
Sub Aggregation - Filters
-
Filter 1
analysis.tags:"com.memsource.analysis.jobPart.raw"
-
Filter 2
analysis.tags:"com.memsource.analysis.jobPart"
-

Monthly TM Leverage

Configuration:
-
Index
analytics.data.analysis
-
Metrics
Sum of data.tm.match.101.words
Enter any match rates from the list
-
Buckets
X-Axis - Date Histogram - Monthly

Projects Created Monthly

Configuration:
-
Index
analytics.data.job
-
Metrics
Unique Count of project.id
-
Buckets
X-Axis - Date Histogram - project.dateCreated - Monthly

Projects Created in Specific Month Sorted by PM

Configuration:
-
Index
analytics.data.job
-
Metrics
Unique Count of project.id
-
Buckets
X-Axis - Date Range - project.dateCreated - dates (in form YYYY-MM-DD)
-
Split charts
Sub Aggregation - Tems
-
Field
job.createdBy.fullName.untouched
-
Order
Top - 0
-
Orderby
metric: Unique count of project.id

Report by LQA category and severity

Configuration:
-
Index
analytics.data.lqa
-
Metrics
Count
-
Buckets
X-Axis - Terms - lqa.category.name
-
Split bars
Sub Aggregation - Terms - lqa.severity.name
