Adding Entity Configurations for Metric Stores
You can use TIBCO BusinessEvents Studio to specify entities that you want to publish to the TIBCO LiveView Web dashboard. You can specify a filter to select only those instances which qualify the filter. Also, for the TIBCO LiveView integration you can specify a trimming rule to trim the LiveView table based on the rule.
- Procedure
- In the BusinessEvents Studio, open the project CDD file for editing and open theCluster tab.
- From the Application Metrics list, select Entity Configurations, and click Add to add an entity configuration.
- Specify the value for the following fields for the new entity and save the agent.
Field Description Entity Uri Browse and select the supported entity that you want to send to the publisher based on your filter. The supported entities are concepts, events, and scorecards. Entity Filter Specify a query to filter out the entity based on your requirement. For example, the following values specifies to send the Account concept to the publisher only when Balance is greater than 10000.
- Entity Uri - /Concepts/Account
- Entity Filter - Balance > 10000
If this field is empty, then all instances of the entity are pushed to the LiveView server.
Tag Entity Id (Only applicable for InfluxDB as a metric store) When enabled entity id is tagged with each measurement.
Default value: selected
Trimming TimeStamp Field (Only applicable for TIBCO LiveView as a metric store) Specify name for an optional timestamp field for your entity. If your entity does not have a timestamp field to write the trimming rule, you can use this field to create a new timestamp field for the entity. This field is part of the LiveView table after generating the LiveView configuration file.
Trimming Rule (Only applicable for TIBCO LiveView as a metric store) Specify a rule to omit the entity data from the LiveView table that matches the trimming rule. The rule can use any field within the entity specified in the Entity Uri field. If required, you can also use Trimming TimeStamp Field for creating rules. Example
OrdStatus=='BAD' when ArrivalTime between epoch() and now()-seconds(6)
where,OrdStatus
is a property of a concept namedAccount
.ArrivalTime
is a property defined in the Trimming TimeStamp Field field.