Elasticsearch tile
About Elasticsearch tiles
The Elasticssearch tile can show data from your Elasticsearch instance. Since Elasticsearch tiles are designed specifically to integrate with Elasticsearch, they offer you a convenient way to access your Elasticsearch indices and enter search queries.
How to configure an Elasticsearch tile
If you don't already have an Elasticsearch provider, you need to create one before you can configure an Elasticsearch tile (How to add an Elasticsearch provider).
- Add a new tile to a dashboard and click on Integrations > Elasticsearch.
- Select the visualization for your Elasticsearch tile and click next.
A Scalar displays one value. A Scalar is useful to show a specific number like "total cost of my services" or "free disk space on this server".
When multiple values are returned (meaning a table with multiple rows), you will still be able to pick the Scalar visualization, but the Scalar will only show the value of the first row.Example:
A table of data, for example incidents or tickets.
Tip: You can turn the individual rows into links in the settings. For example, if you're displaying tickets in your grid, you can link the rows to the ticket in your external ticket system.
Did you know? Since SquaredUp DS 5.4 users can search the grid, and temporarily change the column size and sorting of the grid (by clicking on the column headers) without having to access the settings. They can also expand a row by clicking on the three dots at the end of each row if cells are too small to show their entire content.
Shows time-series data over time, in a graph with an x-axis (time) and a y-axis. You can show several objects, such as servers, in one graph.
Example:
Visualizes time-series data as vertical columns.
Example:
Shows data over time (like line graphs), but each item gets its own graph instead of showing all lines in one graph.
Example:
Visualizes both a number and the resulting bar width based on the number value.
Example:
Shows the results in a donut shape.
Example:
Shows the state of items as icons with different colors. You can display just the icons or together with a description. You can also use a background image and drag the icons into position on the image.
Example:
Shows the state of items as blocks with different colors.
Example:
- Scope
Select the scope for your tile (optional).Tip: If you experience any problems with scoping tiles, you'll find FAQs and help in the article How to scope tiles.
Note: If you never used a perspective, you should read Working with perspectives before scoping tiles on perspectives.
The power of perspectives is that tiles on a perspective can use a dynamic scope. A dynamic scope considers the currently viewed object. A dynamic scope consists of two different states:
- the configuration of the scope in the tile (for example, "consider child objects of type logical disk for the currently viewed object")
- the actual resolved scope that depends on which object you are currently viewing ("this object has 5 child objects of type logical disk")
After configuring the dynamic scope once in the tile, you'll get different results depending how the scope is resolved on the different objects you are viewing.
Suggestions
Suggestions are generated based on the object you are currently viewing. You'll see a list of relevant scope options based on the object's relations to other objects. Suggestions don't cover every possible scope, but they are a quick and easy way to select a suitable scope for your tile.
Note: Suggestions won't be shown if an object has no children, parents or siblings.
Tip: If the exact scope you want isn't listed in the suggestions, you can select a suggested scope that is similar to the one you want, and then click on custom. The custom section will now automatically be filled with the suggestion you picked and you can edit the scope here to adjust it exactly to your needs. This is a more intuitive way to pick a scope than starting in the custom section and navigating the SCOM object model for classes and groups.
Double-check the scope when using suggestions: Using suggestions is an easy way to pick a scope, but you need to make sure that the generated suggestion is appropriate for all objects that use the perspective.
For example, when you pick a suggestion for an EA, you will get suggestions that are specific to the map, dependencies, and availability tests for this one EA. On perspectives you want to use for all EAs, you have to change the scope suggestion in the custom section so that the tile work for all EAs.You can pick between "this object" and objects that are related to this object as parents, children or siblings. The suggestions for children are written as paths that follow the SCOM object tree structure, parents and siblings can be identified by the word parent or sibling in the suggestion.
A parent of an object is any object that hosts or contains that object.
A child of an object is any object that this object hosts or contains.
A sibling of an object is any object of the same class that is hosted by the same parent.Enterprise Applications are designed so that you can map out the servers that make up the application. You can then configure tiles to show information related to just the servers on the EA's map. When you create a perspective that will be used for all EAs, you need to make sure that you scope the tiles so that they work for any EA. When you start with a suggestion, the tile's scope only works for the one EA you're currently looking at, and this is why you need to edit the scope:
- For an EA you want to scope to the servers that are specified on the EA map by selecting something from the suggestions (SquaredUp DS 4.2 and above) that shows something similar to the following:
This /<YourApplicationName> Map / ... / Windows Computer
The above will scope the tile to all the objects of class Windows Computer on this EAs map.
The screenshot below shows some scope suggestions for an application called FinanceXS. The bold text shows the currently selected scope is This object. The cursor shows the optionThis / FinanceXS / ... / Windows Computer
. Once chosen this scope will show all the Windows computers shown on the applications map. Next, we need to adjust the specified scope to allow it to work for all EAs, rather than just this one. - In the scope section click custom.
- Click on the text
<YourApplicationName> Map (children)
which is your first scope step. This will expand the scope step so you can edit it. - Remove the auto-populated class
<YourApplicationName> Map
by clicking the cross x next to it. - Start typing
Enterprise Application - Map
and select this from the list to add this class. This is so that this tile scope will work for all EAs, rather than just this one EA. - The scope is now configured to show all the Windows computers on the EA's map, whichever EA you happen to be viewing with the perspective.
If you are looking at an EA, the path to find all windows computers in that EA may read
Map / ... / Windows Computer
. It returns all objects of the Windows Computer class contained within all of the paths underMap
.To narrow the scope down, you can click on the triangle to expand the suggestion and select one of the more specific paths. If you select
Map / Web / Windows Computer
you will find all objects of the Windows Computer class in the pathMap / Web
.If you choose the option
Map / *
you'll find all objects contained in the map. If you extend this suggestion by clicking on the triangle, you'll see suggestions to select all objects in a more specific path, for exampleMap / Web / *
.Custom
Here you can pick objects that are related to the object you are currently looking at. If you want to create a specific scope that is not listed under suggestions, you can create the scope here.
Tip: You can pick a similar scope under suggestions first and then click on custom to edit it.
- At the top, you'll see the name of the object you are currently looking at. Now you can choose if you want to pick parents or children of that object, and if this parent or child relation should be considered only one level up or down the SCOM model or through all levels.
- Class:
Here you pick the class of the objects you want to select. If you leave this field empty, the scope falls back to the "this object" scope.
Note: You will only see groups and classes that the object you are currently looking at is a member of.
Tip: If you want to pick objects of any class, enter the SCOM base class logical entity in the class field.
Tip: If you want to find out what classes the object you are interested in belongs to, you can go to the Monitored Entity perspective of that object. You'll see all the classes the object belongs to listed there. - Criteria:
You can narrow the selection of objects of a particular class down further by entering criteria for those objects. For more help see How to use criteria when scoping objects.
Tip: If you want to find out what properties you can base your criteria on, you can go to the Monitored Entity perspective of the object you are interested in. You'll see all the properties for criteria listed there.
.
For example, for a perspective created for the group IIS8 Computer Group adding a Status tile scoped to show children with a class of
object
will show the group members, i.e. the members of the IIS8 Computer Group.If you need to traverse a more advanced SCOM object model like an EA, you can use the + button to add more steps. This creates a scope that can go through any kind of path of the SCOM object model.
Complete the following steps and then click the + button after you're done to add the next level of SCOM objects:
- At the top, you'll see the name of the object you are currently looking at. Now you can choose if you want to pick parents or children of that object, and if this parent or child relation should be considered only one level up or down the SCOM model or through all levels.
- Class:
Here you pick the class of the objects you want to select. If you leave this field empty, the scope falls back to the "this object" scope.
Note: You will only see groups and classes that the object you are currently looking at is a member of.
Tip: If you want to pick objects of any class, enter the SCOM base class logical entity in the class field.
Tip: If you want to find out what classes the object you are interested in belongs to, you can go to the Monitored Entity perspective of that object. You'll see all the classes the object belongs to listed there. - Criteria:
You can narrow the selection of objects of a particular class down further by entering criteria for those objects. For more help see How to use criteria when scoping objects.
Tip: If you want to find out what properties you can base your criteria on, you can go to the Monitored Entity perspective of the object you are interested in. You'll see all the properties for criteria listed there.
.
Other specific objects
Gives you the normal, non-dynamic scope options you are used to when scoping tiles on dashboards. This means the tile will not dynamically adapt it's content to the currently viewed object, it will always show data for the static object picked here.
Since the power of perspectives is that their tiles can show data for different objects depending on what object is currently being viewed, you should only select this option when you are sure that there is no relationship between the desired scope and the currently viewed object.
Which status is displayed depends on what you choose as a scope:
- If you want to see the status of individual objects (for example, two individual servers), select multiple objects in the list section.
- If you want to see the status of a group itself rather than the individual objects within the group, select a group in the list section.
- If you want to see the status of each individual group member of a group, select a group in the group section.
- If you want to see the health state of all groups, select the class "group" in the advanced section.
- Provider:
Select your Elasticsearch provider from the select provider drop-down and click next.You can only use providers of the same type as the tile. Providers of other types won't be shown in the select provider drop-down.
- Query:
Index:
Click in the field to see a list of all indices that exist in the Elasticsearch provider you chose. Choose the index or indices you want to use for your tile.
Search type(not for line graphs and sparklines):
Here you enter the search query for the data you want to display. You can choose between the options lucene, where you need to use Lucene query syntax, and query dsl, where you need to use Query DSL syntax. If a simple lucene query is not sufficient for your data request, switch to query dsl to specify your request.
Search(only for line graphs and sparklines):
Here you enter the search query for the data you want to display. You need to use Query DSL syntax. There's already a default query with a simple aggregation in the search field to help you get started.Note: For your queries, you need to know the names of the columns in the index you are using. You can find the column names in your elasticsearch index.If you want to use aggregation:
For using aggregations like an average or a "min/max of the last 20 days for performance scores", your search query must include the
date_histogram
as either the top-level aggregation or as a sub-aggregation. Multiple aggregations are supported. You should setsize
to 0 to make your responses smaller and faster.If you used any kind of aggregation in your search query, you don't need to use the data mapping panel. The tile will automatically do the data mapping based on your search query.
Example:
{ "query": { "query_string": { "query": "" } }, "aggs": { "daily": { "date_histogram": { "field": "timestamp", "calendar_interval": "1d" } } }, "size": 0 }
If you want to use raw data::
You can use raw data (for example, a performance counter for CPU once every 5 minutes), but you'll need to map the raw data in the data mapping panel to display them.
The results of your search must include a numeric value.
Your search query must define the
size
,which controls how many data points you'll get back. You need to make sure that the size is big enough the timeframe and all entities you want to see in the graph.Example: You want to see results for the CPU performance of 3 servers for the last 10 days, and the performance counter collects results once every 5 minutes: 14400 minutes (10 days), divided by 5 minutes (performance counter data collection points) = 2880. Since you want to get results for 3 servers, you need 8640 data points as a
size
.Example:
{ "query": { "query_string": { "query": "" } "size": 8640
The templates button to access search query templates you have created in Elasticsearch. Using a template will copy the search query template into the field, which means that if you make changes to the template in Elasticsearch, those changes will not be automatically pulled into the tile.If you defined a scope you can use the mustache picker to insert scope variables (values that refer only to the defined scope) into your query.
Values that refer to the defined scope carry the prefix
scope.
before the value. For example, you can use the value{{scope[0].displayName}}
for the name of the first item in your scope. You can manipulate the values with javascript syntax. For example, if you want to insert a quoted comma separated list of displayNames from every item in the scope, you can use{{scope.map(item => '"'+item.displayName+'"').join(',')}}
.You can use the clock insert time value button to insert page timeframe and date variables in your query.
The page timeframe is the timeframe setting a dashboard or perspective is currently using. These timeframes are all relative to the current time, for example 7 days ago until now. When a user changes the page timeframe, all tiles that have use page timeframe set will adapt to the new timeframe. (Tiles that do not have use page timeframe set (i.e. are set to specific timeframe or custom timeframe) are not affected and won't change.)
The custom option can be used to set timeframes using ISO 8601 format
SquaredUp DS does not support the week notation.
If you don't use page timeframe variables, the tile will ignore the page timeframe setting by a user.
Available dynamic page timeframe variables
Click next.Available fixed date variables
- Response data (only for bar graphs, donuts, scalars, grids, and status icons or blocks)
Here you can see the response data from the query in the response data field. For most use cases, you need to limit the query response to the specific property you want to use for your data. You pick the property you want to use by entering the key path to the property in the key path field. If you don't need to limit the query result and can use the entire response (for example, if the response data returns the array you want to use at the root of the response), you can leave the key path field empty.
The structure of the response data tells you where to find the property you want to use.
Example:}, "hits": { "total": { "value": 8157, "relation": "eq" },
Click next.
If your response data looks like the example above and you want to display the "value" of "hits", you need to enter hits.total.value in the key path field.
If you want to use the whole array of "hits", you need to enter hits in the key path field. - Settings for the visualization:
Configure the settings for the visualization you chose.Scalar
Color
Conditional formatting:
You can display the data in different colors based on values you define here. For example, you can display the data in green when the value is below 100 and in red when it is above 100.
- Click on add to configure a condition.
- Click on select color.... to open the color picker. Select the color for this condition.
- Enter your condition in the field next to the color. You can use the
value
property and manipulate it with JavaScript String and Regex APIs. When you click on the mustache picker, you'll get some examples:- Value is greater than something, less than something, etc.
For example:{{value < 10}}
(The color you pick will be used if the value is less than 10) - Value is present in the result (scalar tiles only)
For example:value.IndexOf('error') != -1
(The color you pick will be used if the string value "error" is present in the results) - Value matches one of the regular expressions you defined (scalar tiles only)
For example:value.match(/healthy|good|up/)
(The color you picked will be used if the string values arehealthy
,good
, orup
)
- Value is greater than something, less than something, etc.
Display:
Here you decide how the color is used:
Link options
Allows you to turn the graph item(s) into links. You can either enter plain text to create a fixed link (URL always stays the same) or use dynamic properties to create a dynamic link.
Dynamic links make use of dynamic properties which are inserted as part of the URL. This creates a template URL that will be resolved to an actual URL based on the items properties.
For example, if you want to link to tickets in your ticket system and the format of the URL for tickets in your system is
https://www.my-system/ticket-123
, where123
is the ticket ID, you can use the dynamic property that contains the ticket ID and enter the dynamic URLhttps://www.my-system/ticket-{{ticketID}}
.- For scalars, you can only use the dynamic property
value
in dynamic links, which means the link changes when the value of the scalar changes. Since a scalar is just one item, it would also make sense to use a fixed link, for example the link to the website of which you are displaying the response time. - For status icon or bars and the rows of a grid, you usually want to use a dynamic link since you get multiple items or rows that represent different things. You can use any of the dynamic properties the mustache picker offers you.
Dynamic mustache properties and values you need to change according to your instance are highlighted in bold.
ServiceNow incidents:
https://<your-instance>.service-now.com/nav_to.do?uri=%2Fincident.do%3Fsys_id%3D{{sys_id}}
PagerDuty incidents:
{{incident.html_url}}
Azure DevOps projects:
https://dev.azure.com/<your-instance>/{{name}}
Azure DevOps builds:
https://dev.azure.com/<your-instance>/_build/results?buildId={{id}}
Zendesk tickets:
https://<your-instance>.zendesk.com/agent/tickets/{{id}}
Azure Application Insights
https://portal.azure.com/#@squaredup.net/resource/{{ResourceId}}
Grid columns
Grid columns opens the grid designer, where you can show or hide columns, change the order of columns, edit column names or add custom columns.
Property names that contain hyphens (for example
properties.name-with-hyphens
) can't be processed due to a JavaScript limitation. If you want to use a property that contains a hyphen, you have two options:- If you have access to the data source and can change the name of the property, change the name of the property to a name without hyphens.
For example, if your Elasticsearch query uses a property (an aggregation, a grouping or any other property you want to use) with a name that contains a hyphen, you can either access your Elasticsearch instance and change the name there or you can overwrite the name in the query dsl field. - If you can't change the name of the property, you need to enter the property name in the following format:
Original property name:{{properties.name-with-hyphens.value}}
New format:{{properties['name-with-hyphens'].value}}
Grid options
Tip for column sizing: You can change the column width directly in the grid by clicking on the divider lines between columns and dragging them to the width you want. You need to show column headers (by activating the show column headers check box) to be able to change the column width.
Resizing columns while in edit mode affects how the grid looks by default when users open the dashboard. Users can temporarily change the column sizes by dragging them, but those changes only last until they leave the page.Data mapping
If you used any kind of aggregation in your search query, you don't need to use the data mapping panel. The tile will automatically do the data mapping based on your search query.
If you are not using aggregated data, you need to check the display raw data checkbox and map your raw data here:
Property names that contain hyphens (for example
properties.name-with-hyphens
) can't be processed due to a JavaScript limitation. If you want to use a property that contains a hyphen, you have two options:- If you have access to the data source and can change the name of the property, change the name of the property to a name without hyphens.
For example, if your Elasticsearch query uses a property (an aggregation, a grouping or any other property you want to use) with a name that contains a hyphen, you can either access your Elasticsearch instance and change the name there or you can overwrite the name in the query dsl field. - If you can't change the name of the property, you need to enter the property name in the following format:
Original property name:{{properties.name-with-hyphens.value}}
New format:{{properties['name-with-hyphens'].value}}
Top N
Here you can define a limit for the number of results you want to see. Activate the limit number of results displayed checkbox to enter a limit for results. You can choose if this limit should be applied from the top ranking results down (ascending, default option) or from the bottom ranking results up (descending).
Threshold
You can choose to apply a threshold line at a specified value, and whether you wish to fill above or below this value, or just show the line. For example, for free disk space you might want to fill below the line to highlight when space goes below a particular threshold. For processor information you might want to fill above the line to highlight when processor percentage goes above that threshold. The threshold is also shown on the drilldown view.
Max, min, avg
When drilled-down to view a graph, you can select the min, max and avgoptions for each object (displayed to the right of the graph), which displays a line cutting horizontally across the graph a each of the selected value points.
Data range
The Data Range option allows you to choose the range of data the graph will display. For line graphs, this means the data on the y-axis.
Display
Height:
Allows you to set the height of the tile with a slider.
Show hover details:
Shows the value for all lines at any point you hover. There may not be a value exactly where you hover so the value is interpolated from the values either side.
Show points:
Shows where the data points are on the line. Useful to identify missing points, or detail for changing data.
Show trend
Enable the Show Trend Linestoggle to display a trend line for the line graph data. Disable the toggle to hide the trend line.
Custom colors:
You can display the data in different colors based on labels. For example, you can display data in green for a specific user.
- Click on select color.... to open the color picker. Select the color for this condition.
- Enter your condition in the field next to the color. You can use the
label
property and manipulate it with JavaScript String and Regex APIs. When you click on the mustache picker, you'll get some examples:- Condition is true if the label contains something
For example:{{label.indexOf('SQL') != -1}}
(The color you pick will be used if the label contains 'SQL') - Condition is true if the label contains multiple things
For example:{{label.match(/C:|D:|E:/) != null}}
(The color you pick will be used if the label contains 'C:', 'D:' or 'E:') - Condition is true if the label contains multiple things with multiple variations
For example:{{label.match(/^[Ss]erver[0-9]+$/) != null}}
(The color you pick will be used if the label is 'Server' or 'server' with a number after it)
- Condition is true if the label contains something
Label
Allows you to change the label of the results.
Show legend:
Allows you to show or hide the legend of the graph.
Label:
Data mapping
If you used any kind of aggregation in your search query, you don't need to use the data mapping panel. The tile will automatically do the data mapping based on your search query.
If you are not using aggregated data, you need to check the display raw data checkbox and map your raw data here:
Property names that contain hyphens (for example
properties.name-with-hyphens
) can't be processed due to a JavaScript limitation. If you want to use a property that contains a hyphen, you have two options:- If you have access to the data source and can change the name of the property, change the name of the property to a name without hyphens.
For example, if your Elasticsearch query uses a property (an aggregation, a grouping or any other property you want to use) with a name that contains a hyphen, you can either access your Elasticsearch instance and change the name there or you can overwrite the name in the query dsl field. - If you can't change the name of the property, you need to enter the property name in the following format:
Original property name:{{properties.name-with-hyphens.value}}
New format:{{properties['name-with-hyphens'].value}}
Threshold
You can choose to apply a threshold line at a specified value, and whether you wish to fill above or below this value, or just show the line. For example, for free disk space you might want to fill below the line to highlight when space goes below a particular threshold. For processor information you might want to fill above the line to highlight when processor percentage goes above that threshold. The threshold is also shown on the drilldown view.
Data range
The Data Range option allows you to choose the range of data the graph will display. For line graphs, this means the data on the y-axis.
Display
Height:
Allows you to set the height of the tile with a slider.
Show hover details:
Shows the value for all lines at any point you hover. There may not be a value exactly where you hover so the value is interpolated from the values either side.
Solid bars:
Show the bars as solid color or translucent.
Custom colors:
You can display the data in different colors based on labels. For example, you can display data in green for a specific user.
- Click on select color.... to open the color picker. Select the color for this condition.
- Enter your condition in the field next to the color. You can use the
label
property and manipulate it with JavaScript String and Regex APIs. When you click on the mustache picker, you'll get some examples:- Condition is true if the label contains something
For example:{{label.indexOf('SQL') != -1}}
(The color you pick will be used if the label contains 'SQL') - Condition is true if the label contains multiple things
For example:{{label.match(/C:|D:|E:/) != null}}
(The color you pick will be used if the label contains 'C:', 'D:' or 'E:') - Condition is true if the label contains multiple things with multiple variations
For example:{{label.match(/^[Ss]erver[0-9]+$/) != null}}
(The color you pick will be used if the label is 'Server' or 'server' with a number after it)
- Condition is true if the label contains something
Label
Allows you to change the label of the results.
Show legend:
Allows you to show or hide the legend of the graph.
Label:
Data mapping
If you used any kind of aggregation in your search query, you don't need to use the data mapping panel. The tile will automatically do the data mapping based on your search query.
If you are not using aggregated data, you need to check the display raw data checkbox and map your raw data here:
Property names that contain hyphens (for example
properties.name-with-hyphens
) can't be processed due to a JavaScript limitation. If you want to use a property that contains a hyphen, you have two options:- If you have access to the data source and can change the name of the property, change the name of the property to a name without hyphens.
For example, if your Elasticsearch query uses a property (an aggregation, a grouping or any other property you want to use) with a name that contains a hyphen, you can either access your Elasticsearch instance and change the name there or you can overwrite the name in the query dsl field. - If you can't change the name of the property, you need to enter the property name in the following format:
Original property name:{{properties.name-with-hyphens.value}}
New format:{{properties['name-with-hyphens'].value}}
Data Range
The Data Range option allows you to choose the range of data the graph will display. For line graphs, this means the data on the y-axis.
Sort
Sort allows you to change the order of the results displayed. You can sort by value (ascending or descending) or label (alphabetically ascending or descending).
Label
Allows you to change the label of the results.
Color
Data mapping
Property names that contain hyphens (for example
properties.name-with-hyphens
) can't be processed due to a JavaScript limitation. If you want to use a property that contains a hyphen, you have two options:- If you have access to the data source and can change the name of the property, change the name of the property to a name without hyphens.
For example, if your Elasticsearch query uses a property (an aggregation, a grouping or any other property you want to use) with a name that contains a hyphen, you can either access your Elasticsearch instance and change the name there or you can overwrite the name in the query dsl field. - If you can't change the name of the property, you need to enter the property name in the following format:
Original property name:{{properties.name-with-hyphens.value}}
New format:{{properties['name-with-hyphens'].value}}
Data Range
The Data Range option allows you to choose the range of data the graph will display. For line graphs, this means the data on the y-axis.
Sort
Sort allows you to change the order of the results displayed. You can sort by value (ascending or descending) or label (alphabetically ascending or descending).
Value
Value formatter
Allows you to format the value by using the mustache picker. For example, you can round the value up or down or convert it.
Label
Allows you to change the label of the results.
Display
Vertical:
Tick this option to show vertical bars, otherwise horizontal bars are shown.
Bar width:
Allows you to set the width of the bars with a slider.
Color
Data mapping
Property names that contain hyphens (for example
properties.name-with-hyphens
) can't be processed due to a JavaScript limitation. If you want to use a property that contains a hyphen, you have two options:- If you have access to the data source and can change the name of the property, change the name of the property to a name without hyphens.
For example, if your Elasticsearch query uses a property (an aggregation, a grouping or any other property you want to use) with a name that contains a hyphen, you can either access your Elasticsearch instance and change the name there or you can overwrite the name in the query dsl field. - If you can't change the name of the property, you need to enter the property name in the following format:
Original property name:{{properties.name-with-hyphens.value}}
New format:{{properties['name-with-hyphens'].value}}
Sort
Sort allows you to change the order of the results displayed. You can sort by value (ascending or descending) or label (alphabetically ascending or descending).
Value formatter
Allows you to format the value by using the mustache picker. For example, you can round the value up or down or convert it.
Display
Size mode:
Show legend:
Allows you to show or hide the legend of the graph.
Table or Inline:
Show the legend as a separate table or as labels pointing to the segments. When using Inline you can also hide the segment values, and use the slider to change the size of the labels.
Show zero values in legend:
Will show legend items for values of zero which are otherwise missing from the donut.
Fixed height scrollable legend:
Sets the legend to a fixed height where you can scroll through the items. This means that the tile doesn't become too large if there are many items.
Display mode:
Allows you to switch between displaying absolute values or percentages.
Color palette:
Here you can choose between different color palettes.
Note: If there are more items than colors, the colors repeat from the beginning.
Tip for displaying priorities or health states: If you want to display priorities or health states from a data source that doesn't enrich the data with information about priority or health (like the SQL tile or external APIs), use the custom color option and map the results to the correct color. This way, you can make sure that healthy or low priority results are displayed in green, unhealthy or high priority results are displayed in red, etc. If you use the color palettes Priorities, Health1, or Health2 the colors get assigned depending on how the results are sorted, which doesn't guarantee that the colors make sense for the priority or state they represent.
Data mapping
Here you map the status information from your return data to the states of the status icons or blocks. Since every API returns data in a different format, you need to tell the tile where to find the status information and how to interpret it.
Property names that contain hyphens (for example
properties.name-with-hyphens
) can't be processed due to a JavaScript limitation. If you want to use a property that contains a hyphen, you have two options:- If you have access to the data source and can change the name of the property, change the name of the property to a name without hyphens.
For example, if your Elasticsearch query uses a property (an aggregation, a grouping or any other property you want to use) with a name that contains a hyphen, you can either access your Elasticsearch instance and change the name there or you can overwrite the name in the query dsl field. - If you can't change the name of the property, you need to enter the property name in the following format:
Original property name:{{properties.name-with-hyphens.value}}
New format:{{properties['name-with-hyphens'].value}}
- State property:
Here you tell SquaredUp DS where to find the status information in the return data.
Use the mustache picker to select the property from your return data that contains the status information, for example{{status}}
.Note: If you type in the property, make sure you add the mustache
Defining custom states{{}}
to the property name. Otherwise, you'll either get an error message or the property will be interpreted as a static value and be the same for every result.
If your return data doesn't contain a specific state property or you want to use your own categories, you can use JavaScript to define states. This allows you to take your return data and define something like "I want result x (number of open tickets, response time, etc.) to be considered as healthy, otherwise the result should be considered unhealthy."Defining simple custom states
Use case:
Your API returns data with a response time (for example, you monitor servers in Pingdom). You want a response time of over 500 ms to be considered as "Warning", anything else should be considered as "Ok".{{lastresponsetime >= "500" ? "WARNING" : "OK" }}
Mapping:
Result:
You'll see yellow blocks or icons when the response time is over 500 ms and green blocks or icons if the response time is below 500 ms. There will be no red icons or blocks since there is no mapping for "Critical". There will also be no gray blocks since there will be no "Unknown" state, because the return data will always be either below or over 500 ms.Displaying only results of a specific type
Use case:
Your API returns data with a type and a priority (for example, tickets in Zendesk). You only want to see high priority cases. You consider a case high priority when the two fields "type: problem" and "priority: normal" apply to the result. All other results should be ignored.{{#if type == "problem" && priority == "normal"}}HIGHPRIORITY{{else}}IGNORE{{/if}}
Mapping:
The checkbox hide tiles where the state is unknown is activated.
Result:
You'll see red blocks for the cases you defined as high priority. You'll see no green, yellow, or gray blocks, since they have not been mapped and unknown states are hidden.Defining custom states based on multiple conditions
Use case:
Your API returns data with a state and a response time (for example, you monitor servers in Pingdom). You want to define states based on those criteria. If the status is "up", you consider it healthy as long as it is below 65 ms response time. If it is "up" and over 65 ms, you want it to be considered as "warning" in SquaredUp DS (yellow block or icon). If the state in the response data is "warning" instead of "up", you also want it to be considered as "warning". If the state is "down", you want it to be "critical" in SquaredUp DS.{{status === 'up' && lastresponsetime < 65 ? 'Green' : status === 'up' && lastresponsetime > 65 ? 'Yellow' : status === 'warning' ? 'Yellow' : status === 'down' ? 'Red' : 'unknown'}}
Mapping:
Result:
You'll see green blocks or icons (Healthy
) for results with the status "up" and a response time below 65 ms. If the status is "up" but the response time is above 65 ms, you'll see a yellow block or icon (Warning
).
If the status in the response data is "warning" instead of "up", you'll also see a yellow block, since you defined this also a yellow and yellow is mapped toWarning
.
If the status is "down", you'll see a red block (Critical
).
Any other results that don't fit in the categories you defined will be displayed as a gray block or icon (Unknown
).Tip: Since there are two possible causes for the
Warning
state, you want to be able to tell if the status or the response time caused the issue. Use a custom label or sublabel that shows you the status and the response time in your status icon or block to be able to see what caused the warning.Defining custom states with a date and time threshold
Use case:
Your API returns data with a date and time, as well as a type and a priority (for example, tickets in Zendesk). You want tickets of type problem with a normal priority to be acknowledged within 30 mins, which is why you want to see tickets older than 30 mins highlighted in yellow and older than 45 mins highlighted in red.{{#if Date.now() - Date.parse(created_at) >= 1800000 && type == "problem" && priority == "normal" }}30MINS{{elseif Date.now() - Date.parse(created_at) >= 2700000 && type == "problem" && priority == "normal" }}45MINS{{else}}OK{{/if}}
Mapping:
Result:
You'll see tickets that have been created today (Date.now()
), are older than 30 mins (1800000 ms
), and are of the typeproblem
with anormal
priority as yellow blocks or icons since you mapped 30MINS toWarning
. When those tickets are older than 45 mins (2700000
ms), they'll turn red since they are mapped tocritical
. All other tickets will be displayed as green blocks or icons because all other tickets fall into the OK category that is mapped toHealthy
.
There will be no gray (unknown
) blocks or icons since all tickets will fall into one of the custom states you defined. - State mapping:
Here you tell SquaredUp DS how you want the status information to be interpreted.
Map the values of the property from your return data to the states of the status icons or blocks. For example, when the{{status}}
property from your return data can have the valuesgood
,average
andbad
, your mapping would look like this:
Any value that is not mapped to a state will be interpreted asunknown
.
The mapped state values define the color of the status icons or blocks:
Link options
item link:
Allows you to turn the graph item(s) into links. You can either enter plain text to create a fixed link (URL always stays the same) or use dynamic properties to create a dynamic link.
Dynamic links make use of dynamic properties which are inserted as part of the URL. This creates a template URL that will be resolved to an actual URL based on the items properties.
For example, if you want to link to tickets in your ticket system and the format of the URL for tickets in your system is
https://www.my-system/ticket-123
, where123
is the ticket ID, you can use the dynamic property that contains the ticket ID and enter the dynamic URLhttps://www.my-system/ticket-{{ticketID}}
.- For scalars, you can only use the dynamic property
value
in dynamic links, which means the link changes when the value of the scalar changes. Since a scalar is just one item, it would also make sense to use a fixed link, for example the link to the website of which you are displaying the response time. - For status icon or bars and the rows of a grid, you usually want to use a dynamic link since you get multiple items or rows that represent different things. You can use any of the dynamic properties the mustache picker offers you.
Dynamic mustache properties and values you need to change according to your instance are highlighted in bold.
ServiceNow incidents:
https://<your-instance>.service-now.com/nav_to.do?uri=%2Fincident.do%3Fsys_id%3D{{sys_id}}
PagerDuty incidents:
{{incident.html_url}}
Azure DevOps projects:
https://dev.azure.com/<your-instance>/{{name}}
Azure DevOps builds:
https://dev.azure.com/<your-instance>/_build/results?buildId={{id}}
Zendesk tickets:
https://<your-instance>.zendesk.com/agent/tickets/{{id}}
Azure Application Insights
https://portal.azure.com/#@squaredup.net/resource/{{ResourceId}}
Property names that contain hyphens (for example
properties.name-with-hyphens
) can't be processed due to a JavaScript limitation. If you want to use a property that contains a hyphen, you have two options:- If you have access to the data source and can change the name of the property, change the name of the property to a name without hyphens.
For example, if your Elasticsearch query uses a property (an aggregation, a grouping or any other property you want to use) with a name that contains a hyphen, you can either access your Elasticsearch instance and change the name there or you can overwrite the name in the query dsl field. - If you can't change the name of the property, you need to enter the property name in the following format:
Original property name:{{properties.name-with-hyphens.value}}
New format:{{properties['name-with-hyphens'].value}}
Label
Allows you to change the label of the results.
Sublabel
Allows you to add a sublabel of the results.
Sort
Sort allows you to change the order of the results displayed. You can also group them by their characteristics.
Limit:
Allows you to define a maximum number of objects that will be shown. When 'group by' is used the limit applies to each group individually, for example to show 10 objects in each health state.
Image
Here you can choose one of the provided images or upload your own.
Tip: If you want a different selection of maps, you can download more at https://freevectormaps.com/Supported image formats: png, jpg, jpeg, gif, tif, tiff. svg, bmp
Tip: SVG images resize best since they are vector images.File size limit: 10MB
Image size: Images fill the size of the tile, which means you can resize the image by adjusting the tile's size. The size of the tile also depends on the screen the dashboard is being viewed on.
Icons
Here you can customize the icons on the image:
- You can change the size of the icons with the slider
- You can change the shape of the icons (square or circle)
- You can drag the icons on the image into position
Display styles for Status icons
This setting is not done in a panel, you can change the display style even after you finished configuring the tile.
You can use toggle zoom button at the top right of the tile to change between the different ways Status icons can be displayed.
Data mapping
Here you map the status information from your return data to the states of the status icons or blocks. Since every API returns data in a different format, you need to tell the tile where to find the status information and how to interpret it.
Property names that contain hyphens (for example
properties.name-with-hyphens
) can't be processed due to a JavaScript limitation. If you want to use a property that contains a hyphen, you have two options:- If you have access to the data source and can change the name of the property, change the name of the property to a name without hyphens.
For example, if your Elasticsearch query uses a property (an aggregation, a grouping or any other property you want to use) with a name that contains a hyphen, you can either access your Elasticsearch instance and change the name there or you can overwrite the name in the query dsl field. - If you can't change the name of the property, you need to enter the property name in the following format:
Original property name:{{properties.name-with-hyphens.value}}
New format:{{properties['name-with-hyphens'].value}}
- State property:
Here you tell SquaredUp DS where to find the status information in the return data.
Use the mustache picker to select the property from your return data that contains the status information, for example{{status}}
.Note: If you type in the property, make sure you add the mustache
Defining custom states{{}}
to the property name. Otherwise, you'll either get an error message or the property will be interpreted as a static value and be the same for every result.
If your return data doesn't contain a specific state property or you want to use your own categories, you can use JavaScript to define states. This allows you to take your return data and define something like "I want result x (number of open tickets, response time, etc.) to be considered as healthy, otherwise the result should be considered unhealthy."Defining simple custom states
Use case:
Your API returns data with a response time (for example, you monitor servers in Pingdom). You want a response time of over 500 ms to be considered as "Warning", anything else should be considered as "Ok".{{lastresponsetime >= "500" ? "WARNING" : "OK" }}
Mapping:
Result:
You'll see yellow blocks or icons when the response time is over 500 ms and green blocks or icons if the response time is below 500 ms. There will be no red icons or blocks since there is no mapping for "Critical". There will also be no gray blocks since there will be no "Unknown" state, because the return data will always be either below or over 500 ms.Displaying only results of a specific type
Use case:
Your API returns data with a type and a priority (for example, tickets in Zendesk). You only want to see high priority cases. You consider a case high priority when the two fields "type: problem" and "priority: normal" apply to the result. All other results should be ignored.{{#if type == "problem" && priority == "normal"}}HIGHPRIORITY{{else}}IGNORE{{/if}}
Mapping:
The checkbox hide tiles where the state is unknown is activated.
Result:
You'll see red blocks for the cases you defined as high priority. You'll see no green, yellow, or gray blocks, since they have not been mapped and unknown states are hidden.Defining custom states based on multiple conditions
Use case:
Your API returns data with a state and a response time (for example, you monitor servers in Pingdom). You want to define states based on those criteria. If the status is "up", you consider it healthy as long as it is below 65 ms response time. If it is "up" and over 65 ms, you want it to be considered as "warning" in SquaredUp DS (yellow block or icon). If the state in the response data is "warning" instead of "up", you also want it to be considered as "warning". If the state is "down", you want it to be "critical" in SquaredUp DS.{{status === 'up' && lastresponsetime < 65 ? 'Green' : status === 'up' && lastresponsetime > 65 ? 'Yellow' : status === 'warning' ? 'Yellow' : status === 'down' ? 'Red' : 'unknown'}}
Mapping:
Result:
You'll see green blocks or icons (Healthy
) for results with the status "up" and a response time below 65 ms. If the status is "up" but the response time is above 65 ms, you'll see a yellow block or icon (Warning
).
If the status in the response data is "warning" instead of "up", you'll also see a yellow block, since you defined this also a yellow and yellow is mapped toWarning
.
If the status is "down", you'll see a red block (Critical
).
Any other results that don't fit in the categories you defined will be displayed as a gray block or icon (Unknown
).Tip: Since there are two possible causes for the
Warning
state, you want to be able to tell if the status or the response time caused the issue. Use a custom label or sublabel that shows you the status and the response time in your status icon or block to be able to see what caused the warning.Defining custom states with a date and time threshold
Use case:
Your API returns data with a date and time, as well as a type and a priority (for example, tickets in Zendesk). You want tickets of type problem with a normal priority to be acknowledged within 30 mins, which is why you want to see tickets older than 30 mins highlighted in yellow and older than 45 mins highlighted in red.{{#if Date.now() - Date.parse(created_at) >= 1800000 && type == "problem" && priority == "normal" }}30MINS{{elseif Date.now() - Date.parse(created_at) >= 2700000 && type == "problem" && priority == "normal" }}45MINS{{else}}OK{{/if}}
Mapping:
Result:
You'll see tickets that have been created today (Date.now()
), are older than 30 mins (1800000 ms
), and are of the typeproblem
with anormal
priority as yellow blocks or icons since you mapped 30MINS toWarning
. When those tickets are older than 45 mins (2700000
ms), they'll turn red since they are mapped tocritical
. All other tickets will be displayed as green blocks or icons because all other tickets fall into the OK category that is mapped toHealthy
.
There will be no gray (unknown
) blocks or icons since all tickets will fall into one of the custom states you defined. - State mapping:
Here you tell SquaredUp DS how you want the status information to be interpreted.
Map the values of the property from your return data to the states of the status icons or blocks. For example, when the{{status}}
property from your return data can have the valuesgood
,average
andbad
, your mapping would look like this:
Any value that is not mapped to a state will be interpreted asunknown
.
The mapped state values define the color of the status icons or blocks:
Link options
item link:
Allows you to turn the graph item(s) into links. You can either enter plain text to create a fixed link (URL always stays the same) or use dynamic properties to create a dynamic link.
Dynamic links make use of dynamic properties which are inserted as part of the URL. This creates a template URL that will be resolved to an actual URL based on the items properties.
For example, if you want to link to tickets in your ticket system and the format of the URL for tickets in your system is
https://www.my-system/ticket-123
, where123
is the ticket ID, you can use the dynamic property that contains the ticket ID and enter the dynamic URLhttps://www.my-system/ticket-{{ticketID}}
.- For scalars, you can only use the dynamic property
value
in dynamic links, which means the link changes when the value of the scalar changes. Since a scalar is just one item, it would also make sense to use a fixed link, for example the link to the website of which you are displaying the response time. - For status icon or bars and the rows of a grid, you usually want to use a dynamic link since you get multiple items or rows that represent different things. You can use any of the dynamic properties the mustache picker offers you.
Dynamic mustache properties and values you need to change according to your instance are highlighted in bold.
ServiceNow incidents:
https://<your-instance>.service-now.com/nav_to.do?uri=%2Fincident.do%3Fsys_id%3D{{sys_id}}
PagerDuty incidents:
{{incident.html_url}}
Azure DevOps projects:
https://dev.azure.com/<your-instance>/{{name}}
Azure DevOps builds:
https://dev.azure.com/<your-instance>/_build/results?buildId={{id}}
Zendesk tickets:
https://<your-instance>.zendesk.com/agent/tickets/{{id}}
Azure Application Insights
https://portal.azure.com/#@squaredup.net/resource/{{ResourceId}}
Property names that contain hyphens (for example
properties.name-with-hyphens
) can't be processed due to a JavaScript limitation. If you want to use a property that contains a hyphen, you have two options:- If you have access to the data source and can change the name of the property, change the name of the property to a name without hyphens.
For example, if your Elasticsearch query uses a property (an aggregation, a grouping or any other property you want to use) with a name that contains a hyphen, you can either access your Elasticsearch instance and change the name there or you can overwrite the name in the query dsl field. - If you can't change the name of the property, you need to enter the property name in the following format:
Original property name:{{properties.name-with-hyphens.value}}
New format:{{properties['name-with-hyphens'].value}}
Label
Allows you to change the label of the results.
Sublabel
Allows you to add a sublabel of the results.
Sort
Sort allows you to change the order of the results displayed. You can also group them by their characteristics.
Limit:
Allows you to define a maximum number of objects that will be shown. When 'group by' is used the limit applies to each group individually, for example to show 10 objects in each health state.
Blocks
Here you can set the number of columns for the blocks, their height and the font size within the blocks.
Click done to save the tile.
The tile now shows data according to your settings.