2 Replies Latest reply: Feb 23, 2011 12:05 AM by seeruk RSS

    WANT TO KNOW MORE ON TABLE STRUCTURE OF: HQ_METRIC_DATA

    Vembu_hyperic Hot Shot
      Hi,

      I wanted to know in HQ, how they are storing values in hq_metric_data_**_**:
      as well the logic they are using to dynamically store values in to metric_data table. so that i can have a copy of data history.am already aware of hr and d data of measurement_1H etc...

      Can any one tell me how can i assume that tomm the metric value will be stored in so and so table...
        • 1. Re: WANT TO KNOW MORE ON TABLE STRUCTURE OF: HQ_METRIC_DATA
          fon_hyperic Hot Shot
          bump.   this would be very useful.
          • 2. Re: WANT TO KNOW MORE ON TABLE STRUCTURE OF: HQ_METRIC_DATA
            seeruk Hot Shot
            HQ_METRIC_DATA is a view. The view includes all the HQ_METRIC_DATA_* (1h, 6h 1d etc) tables which means that it is GINORMOUS!

            I presume you are tackling a similar issue to all of us. That is given the fact there is NO REPORTING TOOL anymore you are having to write custom code or jsp's to replace this very basic functionality.

            Using the HQ_METRIC_DATA view for any queries is very inefficient and slow due to it's size.

            The real mystery and something that has never been explained as far as I can tell is the tables named so:

            hq_metric_data_0d_0s
            hq_metric_data_0d_1s
            hq_metric_data_1d_0s
            hq_metric_data_1d_1s
            hq_metric_data_2d_0s
            hq_metric_data_2d_1s
            etc etc

            Looking just from a logical naming perspective they would seem to refer to the age of the data making them great for development purposes (like only needing to query one smaller table of data for yesterday etc) but it turns out that data seems to rotate through these table seemingly at random. So one day, yesterdays data will be in 1d1s then tomorrow I might find yesterdays data in 3d1s or something

            If we could understand how data flows through these tables then I am sure it would help us poor developers who are trying to replace functionality WE PAID FOR.