Viewing Event properties as a table

prerequisites before displaying events in grafana, ensure configuring an event docid\ e9bjftgiz2m1bxqppz3qx in factry historian configuring the factry historian datasource plugin for grafana docid\ q9t7hxoxsknylawporfdd is correctly set up in grafana to learn more about events , consult the concepts documentation why use the factry datasource for simple properties? the factry grafana datasource is built to make event data exploration simple it allows you to query events and their simple properties directly, without writing custom sql display events as tabular overviews with start/end times and context use built in support for assets and where filters to focus on the data that matters seamlessly combine event data with time series data for end to end process analysis default usage to display simple properties of events, either create a new dashboard or use the explore functionality open or create a new table panel in grafana select the factry historian datasource plugin as the data source if it's not selected by default, then select the events tab select simple as the query type select an asset (with events configured on it) from the asset tree by clicking the assets field select the event type select the event's simple properties from the properties field optionally filter on status (e g only processed events) optionally include a viewing event properties as a table /#filtering event tables by event values optionally include simple properties from parent events filtering event tables by event values event tables often contain many runs filters help you focus on the relevant ones filter by asset → use the assets field in the query editor filter by other event properties → use the where clause syntax where \<column> = \<value> where \<column> in ('value1', 'value2') examples where product = 'ipa' where batchid in ('12345', '12346') where shift = 'night' where usage >= 5 transforming timestamps event start and end times are returned in utc timestamp format to display them in a user friendly way in the panel editor, go to transform add a convert field type transformation select the timestamp fields and format them as date/time if you filter on event state, exclude open events (events that are still running) otherwise, the missing end time may cause errors in timestamp transformations