Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Softlayer metric tracking object stopped returning summary data #24

Open
tasso85 opened this issue Apr 6, 2017 · 0 comments
Open

Softlayer metric tracking object stopped returning summary data #24

tasso85 opened this issue Apr 6, 2017 · 0 comments

Comments

@tasso85
Copy link

tasso85 commented Apr 6, 2017

I recently developed a script to monitor all of our virtual servers on the IBM SoftLayer infrastructure.

The script relies on their public API, specifically on the SoftLayer_Metric_Tracking_Object service and its getSummaryData method; it all worked correctly for the last few months, but now the script gets nothing but empty responses.

I have checked that the API access itself happens correctly, in fact the script is able to query the virtual servers data (CPU, RAM size, ecc.), however the call to get the summary of metric data always fails with no error, just an empty array being returned.

As an example, here are the parameters used in one such call:

startDateTime = "2017-04-06T07:22:48+02:00"
endDateTime   = "2017-04-06T10:22:48+02:00"
validTypes    = array(3) {
    [0]=>
    object(stdClass)#283 (2) {
        ["keyName"]=>
        string(12) "MEMORY_USAGE"
        ["summaryType"]=>
        string(7) "average"
    }
    [1]=>
    object(stdClass)#282 (2) {
        ["keyName"]=>
        string(4) "CPU0"
        ["summaryType"]=>
        string(7) "average"
    }
    [2]=>
    object(stdClass)#281 (2) {
        ["keyName"]=>
        string(4) "CPU1"
        ["summaryType"]=>
        string(7) "average"
    }
}
summaryPeriod = 3600

After initial deployment I did not change the script, which now stopped working, and I'd like to know why it did, more specifically if it is perhaps called with, as of now, wrong parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant