Querying Instances
  • 02 Sep 2022
  • 4 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Querying Instances

  • Dark
    Light
  • PDF

  • Consider the following scenario: the user has their solution up and running and is using Serverless360 Business Activity Monitoring to manage it. The billion-dollar question that corporate users frequently ask is, "Where is the message?"

  • A Query search is a solution to this issue.

  • Users can easily search for transactions on the Tracking section using the Business Activity Monitoring search language query provided. A business process is associated with a Business Application. The process has transactions flowing through it, and tracked properties are enabled.

  • Assume a user has some transactions and wants to search for a certain transaction; if the user types Transaction in the Search field, the user will get IntelliSense for it.

6Tracking-Transaction_instances-Querying_Instances-QuerySearch-1stimg.png

  • Users can see the completed transactions that have been entered in the search bar once they have entered the full query and hit search.

failure.png

  • The tracking search results will display the latest 1000 records of transaction instances for a given business process, which are organized in descending order based on the transaction instance's start time.

  • The number of records displayed per page can also be customized by entering the required value in the Select Top field. Clicking on the Next button in the footer displays the next set of records if available.

failure.png

  • Query search can be performed to display the latest (or) oldest records. For example, Order by = "ascending" query fetches all the oldest records first with respect to the number of records to be displayed.

asc.png

Query Language

Serverless360 features a Domain-Specific Language that users can use to search for activities. All the properties set up in the business process configuration page will be searchable, and users will be notified if any query elements are incorrect.

Following are some examples of queries:

Searching for an exact match

  • SenderId = "Milford"

Searching for a partial match

  • SenderId like "%Milford%"

Searching for integer property using comparison operators

  • Price > 10

Searching using combinations

  • SenderId = "Milford" and Price > 10

Searching using groupings

  • (SenderId="Milford" and Price > 10) or (ReceiverId="Miles" and Price<10)

Searching for assigned transactions

  • AssignedTo = "me"

  • AssignedTo = "mail_id"

    These two queries support only in Assigned Transactions tab.

Search using status and duration

  • Status = "inprogress" and TransactionDuration > "1min"
  • Customers can now easily perform query searches by simply entering a value in the query field rather than the entire query.

  • In order to generate query data for Integer data types, the input value must be entered without double quotes (").

  • The query value for String data types must be enclosed in double quotation marks (").

  • The query data for Date type can be generated by simply entering "getdate(MM/dd/yyyy HH:mm:ss)" in the query field.

date.gif

Search based on elapsed time

Serverless360 Business Activity Monitoring also supports the option to query the transaction instances based on the elapsed time of the transaction.

The elapsed time is shown in the Duration column on the tracking page.

This search query can also be used in Query monitors to monitor the Duration of the transaction.

Following are some queries based on elapsed time:

  • TransactionDuration < "1 ms"

  • TransactionDuration < "1 s"

  • TransactionDuration < "1 min"

  • TransactionDuration < "1 hr"

  • TransactionDuration < "1 d"

Search based on exceptions

Users can now query transaction instances based on exception code and exception message in Serverless360 Business Activity Monitoring.

Users can use this search query to track transaction instances with exceptions.

Pre-requisites

Before beginning this query search, make sure to meet the following requirements:

1. Creating global properties for exceptioncode and exceptionmessage

  • Users must define global properties for exceptioncode and exceptionmessage, with data types of NUMBER and STRING, respectively.

Global properties.png

Refer to this article for creating global properties.

2. Configuring global properties to a Stage in the desired Transaction

  • The next step is to assign the newly created global properties to a stage in the desired transaction.

querying instance2.gif

Query search

Following are some queries based on exceptions:

  • exceptioncode = 100

  • exceptionmessage = "exception100"

  • exceptionmessage like "%exce%"

Search based on tags

Users can also query transaction instances based on the tags attached to them.

Ignored and Reprocessed are two of the available tags.

The following are some queries based on tags:

  • Reprocessed = "true"

  • Ignored = "false"

  • Reprocessed = "false"

  • Ignored = "true"

Search based on date properties

  • Serverless360 allows users to search the properties of the Data Type Date in a much easier way. Such properties can be searched by using the getDate() function in the Search Query.

  • For example, if a user wants to raise the invoices raised before 04/25/2020 09:24:26 then the user can use the Search Query.

Date Time Format

MM/DD/YYYY HH:mm:ss

RaisedAt <= "getdate(04/25/2020 09:24:26)"

RaisedAt is the name of the tracked property and the data type of the property is Date.

If there is a need to search the tracked data based on the current time, we can use the following Search Query.

RaisedAt <= "currenttime()"

Save a Query

  • Customers can also save their queries in the Tracking section available within the business process in the Explorer View with the help of Save button.

  • Provide a query search for a specified time period and then click Save button once the query data is generated. Enter a name for the query and click Save. Users can find their saved queries using Saved queries option available at the top.

  • The user is also provided with a checkbox in the Save search blade to set the Query as default.

Saving Query.gif

Import / Export a Query

  • Users can import queries from any of the downloaded Query file that is in JSON format with the help of the Import button present in the Saved queries blade.

  • The saved queries can also be exported as a JSON file with the help of the Export button present in the Saved queries blade.

importexport.gif

If the user does not provide a name, the query will be given an auto-generated name using time and date data.


Was this article helpful?