EcoStruxure IT forum
A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.
Posted: 2020-07-03 10:37 PM
This question was originally posted on DCIM Support by Lukasz Staciwo on 2017-09-06
Hi Team,
Asking on behalf of jared reed.
DCE is running v7.4.1.5.
They tried to upgrade to 7.4.3 but are experiencing issues during upgrade (separaete post on this here: )
Jared asked me the following question could you please assist:
__________
I have a tricky problem to do with trend data received from DCE following a query.
See below we run the trend request, however the data returned is from June…. Is there something were missing here?
We would expect the returned data to be most recent, I have check times on devices and server they are correct.
“
Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2">
<soapenv:Header/>
<soapenv:Body>
<isx:getHistoricalSensorDataRequest>
<isx:ISXCElementID>B8D8670_nbAlinkEnc_0_1_TEMP</isx:ISXCElementID>
</isx:getHistoricalSensorDataRequest>
</soapenv:Body>
</soapenv:Envelope>
Response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body xmlns:ns1="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2">
<ns1:getHistoricalSensorDataResponse>
<ns1:ArrayOfISXCSensorData>
<ns2:ISXCSensorData xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">
<ns2:timeStamp>2017-06-26T14:18:52.225+08:00</ns2:timeStamp>
<ns2:units>° C</ns2:units>
<ns2:value>24.1</ns2:value>
<ns2:ISXCValueType>FLOAT</ns2:ISXCValueType>
</ns2:ISXCSensorData>
<ns2:ISXCSensorData xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">
<ns2:timeStamp>2017-06-26T14:19:54.940+08:00</ns2:timeStamp>
<ns2:units>° C</ns2:units>
<ns2:value>24.0</ns2:value>
<ns2:ISXCValueType>FLOAT</ns2:ISXCValueType>
“
(CID:124523221)
Posted: 2020-07-03 10:37 PM
This answer was originally posted on DCIM Support by Christopherus Laurentius on 2017-09-06
Hey Luke, just on the SOAP part,
-Hi all, do correct me if i misunderstood this particular getHistoriclaSensorData request.
I'd recommend you to indicate the startDate and endDate, if you want historical data on specific date, as the number of data returned is <1000, see the max data points description.
To get historical data until the last available data, indicate 'null' as endDate, but ensure you have start date, and estimate so the total data points returned is less than 1000.
For example if the sensor is polled every 5 minutes, in a day you'll have 24 x 60 / 5 or 288 entries.
(plus additional entries when the device has alarm, and DCE polled it)
Netbotz will have more, as some of them have entries every minute, so that's 1,440 data points daily.
Some alternatives, depending on what user wants to achieve use:
getAverageSensorDataReturns an ISXCSensorData object that represents the average value of recorded data for a sensor with the specified ID.
getSensorData
Returns an ISXCSensorData object that represents the current value data for the sensor with the specified ID.
See explanation below on getHistoricalSensorData
As comparison,below is a similar response:
(CID:124523233)
Posted: 2020-07-03 10:37 PM
This answer was originally posted on DCIM Support by Christopherus Laurentius on 2017-09-06
Hey Luke, just on the SOAP part,
-Hi all, do correct me if i misunderstood this particular getHistoriclaSensorData request.
I'd recommend you to indicate the startDate and endDate, if you want historical data on specific date, as the number of data returned is <1000, see the max data points description.
To get historical data until the last available data, indicate 'null' as endDate, but ensure you have start date, and estimate so the total data points returned is less than 1000.
For example if the sensor is polled every 5 minutes, in a day you'll have 24 x 60 / 5 or 288 entries.
(plus additional entries when the device has alarm, and DCE polled it)
Netbotz will have more, as some of them have entries every minute, so that's 1,440 data points daily.
Some alternatives, depending on what user wants to achieve use:
getAverageSensorDataReturns an ISXCSensorData object that represents the average value of recorded data for a sensor with the specified ID.
getSensorData
Returns an ISXCSensorData object that represents the current value data for the sensor with the specified ID.
See explanation below on getHistoricalSensorData
As comparison,below is a similar response:
(CID:124523233)
Posted: 2020-07-03 10:37 PM
This comment was originally posted on DCIM Support by Lukasz Staciwo on 2017-09-06
Thanks Chris,
I will get Jared to review ans he can come back to you with additional questions.
(CID:124523269)
Posted: 2020-07-03 10:37 PM
This comment was originally posted on DCIM Support by jared reed on 2017-09-07
Chris, Lukaz,
This is great, we have simply limited our start time parameter to 24hr prior to origin(current time).
This is providing the last 1000 records from the last 24hrs.
ANSWERED thank you
(CID:124524165)
Posted: 2020-07-03 10:37 PM
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.