Topic
  • 5 replies
  • Latest Post - ‏2014-02-05T13:32:19Z by IsaacGraf
kftiv
kftiv
15 Posts

Pinned topic Presenting table data in a TBSM view

‏2014-01-20T16:23:53Z |

Dear all,

 

We have several situations in which we would like to present information for a specific service instance in a table-like view. The information we're looking for is available via a data fetcher or via an Impact Data Source. Examples are the result of an ITM Query to present in a TBSM view and the result of a data fetcher query to obtain a subset of incident details (id, summary, severity, status) for a service instance in TBSM (matching the "Affected Item") in the incident registration system.

I've looked for portlet types that could be used, but haven't found anything that seems to fit (e.g. Table View, Views, TBSM Charting), but nothing seems to fit. Preferrably the table should be linked by a "wire" to present the information related to the selected service instance.

Help in handling this would be greatly appreciated. Unfortunately we do not have DASH available (yet), so we need to handle this within the capabilities of the TBSM Dashboard Server.

Thx

Updated on 2014-02-18T15:11:49Z at 2014-02-18T15:11:49Z by kftiv
  • sdiering
    sdiering
    16 Posts

    Re: Presenting table data in a TBSM view

    ‏2014-01-20T17:08:16Z  

    how much data do you want to display in your table-like view?

    1. rows
    2. columns

    steve

     

  • kftiv
    kftiv
    15 Posts

    Re: Presenting table data in a TBSM view

    ‏2014-01-20T19:05:08Z  
    • sdiering
    • ‏2014-01-20T17:08:16Z

    how much data do you want to display in your table-like view?

    1. rows
    2. columns

    steve

     

    Steve (and others),

    Actually the amount of data varies for the different uses. For incidents per service instance we'd expect around 4 to 6 columns (see above: incident id, summary, severity, status, etc.) and the number of incidents to display will vary (maybe between 0 to 40 incidents). For other cases, to present ITM6 data, this will probably be like 10 to 15 attributes and also 10 to 15 rows.

    But since you're asking, I assume the approach is different depending on the amount of data. Please explain so we can make the right choices.

    Thx

  • randybrown
    randybrown
    60 Posts

    Re: Presenting table data in a TBSM view

    ‏2014-01-24T21:20:53Z  
    • kftiv
    • ‏2014-01-20T19:05:08Z

    Steve (and others),

    Actually the amount of data varies for the different uses. For incidents per service instance we'd expect around 4 to 6 columns (see above: incident id, summary, severity, status, etc.) and the number of incidents to display will vary (maybe between 0 to 40 incidents). For other cases, to present ITM6 data, this will probably be like 10 to 15 attributes and also 10 to 15 rows.

    But since you're asking, I assume the approach is different depending on the amount of data. Please explain so we can make the right choices.

    Thx

    Hello,

    For TBSM the closest thing to a table-like view is our Service Tree portlet, which you can customize to show columns of your choosing with Tree Templates. It is by definition a tree, but if the services you are showing are "leaf" nodes, then you would have a "flat" representation.

    However, for this TBSM tree (also commonly referred to as a "scorecard") you would have one row per service. On this row you can map metrics from any templates you have assigned to the service, and these metrics would be values you were able to collect from your data fetchers or rules you might implement with Impact policies and data types.

    You would be able to change the context of this tree by clicking on another tree or view to change the "starting" service. But it sounds like you would need to launch from this tree to another tool, for example, the source of the incidents you wish to display.

    This can be accomplished by adding context menus to TBSM to launch out to other tools. With a more advanced configuration of the service tree, it is also possible to launch out directly from a link you embed in one of the columns of the service tree.

    I hope this gives you an overview of what TBSM can do based on our understanding of your requirements.

    Regards...

     

    Randy Brown

  • kftiv
    kftiv
    15 Posts

    Re: Presenting table data in a TBSM view

    ‏2014-02-04T20:56:52Z  

    Hello,

    For TBSM the closest thing to a table-like view is our Service Tree portlet, which you can customize to show columns of your choosing with Tree Templates. It is by definition a tree, but if the services you are showing are "leaf" nodes, then you would have a "flat" representation.

    However, for this TBSM tree (also commonly referred to as a "scorecard") you would have one row per service. On this row you can map metrics from any templates you have assigned to the service, and these metrics would be values you were able to collect from your data fetchers or rules you might implement with Impact policies and data types.

    You would be able to change the context of this tree by clicking on another tree or view to change the "starting" service. But it sounds like you would need to launch from this tree to another tool, for example, the source of the incidents you wish to display.

    This can be accomplished by adding context menus to TBSM to launch out to other tools. With a more advanced configuration of the service tree, it is also possible to launch out directly from a link you embed in one of the columns of the service tree.

    I hope this gives you an overview of what TBSM can do based on our understanding of your requirements.

    Regards...

     

    Randy Brown

    Randy, thanks for your reply. I considered the Tree Template Editor, but it would require that we have a TBSM service instance configured for each incident to allow us to show incident details like incident number, brief description, severity, status. To me this sounds like a bit of overhead since the only goal is to present these incident details. It is an approach also described in the TBSM Scenarios guide though. I did discover a way though which we might be able to use. It's the TBSM Charts approach which apparently also has the opportunity to present the data in a table view and also allows for parameterization based on the service instance (using __param__ in the WHERE clause).

    Any comments on this approach?

    Regards..

  • IsaacGraf
    IsaacGraf
    34 Posts

    Re: Presenting table data in a TBSM view

    ‏2014-02-05T13:32:19Z  
    • kftiv
    • ‏2014-02-04T20:56:52Z

    Randy, thanks for your reply. I considered the Tree Template Editor, but it would require that we have a TBSM service instance configured for each incident to allow us to show incident details like incident number, brief description, severity, status. To me this sounds like a bit of overhead since the only goal is to present these incident details. It is an approach also described in the TBSM Scenarios guide though. I did discover a way though which we might be able to use. It's the TBSM Charts approach which apparently also has the opportunity to present the data in a table view and also allows for parameterization based on the service instance (using __param__ in the WHERE clause).

    Any comments on this approach?

    Regards..

    Hi,

    The __param__ in the where clause for the charts works if you want to display data from a database query. Then you can parameterize the query based on properties in the service instance that you click on. So if you can construct a query to get the data, then that approach should work. You can also write an Impact policy to get the data for a chart and the policy has access to the properties in the instance click on.

    Regards,

    Isaac