Getting Started Guide

This guide provides instructions for using the Compute Ops Management APIs to analyze an Active Health System (AHS) log file.

1. Review the prerequisites

Verify that the prerequisites are met before starting the analysis. For more information, see AHS Log Prerequisites.

2. Upload the AHS file

Use the following steps to upload an AHS file for analysis.

Create a pre-signed URL

A pre-signed URL can be created by issuing a POST to the /compute-ops-mgmt/v1beta1/ahs-files endpoint with the correct payload for the task. The following properties are used when creating a pre-signed URL task:

Method	API	Property	JSON Type	Description	Required
POST	`/compute-ops-mgmt/v1beta1/ahs-files`	`fileName`	string	AHS file name which will be uploaded using pre-signed URL	Yes

A sample payload to create a pre-signed URL for an AHS file is shown below:

Copy

Copied

{
    "fileName": "DL20_Gen9.ahs"
}

The pre-signed URL allows the user to upload the selected file directly and securely to the Compute Ops Management data store provided by Amazon Web Services (AWS) Simple Storage Service (S3).

note

The pre-signed URL is valid for a maximum of 10 minutes. The user must upload the file within this time period, or the link will expire, and the upload will fail.

A response sample from the POST follows:

Copy

Copied

{
    "id": "2da59d25-72e7-4052-afd3-f20fc8e6d0b7",
    "type": "compute-ops-mgmt/ahs-file",
    "baseUrl": "https://dev-hpecomputesupport-us-west-2.s3.amazonaws.com/",
    "parameters": [
        {
            "name": "key",
            "value": "AHS_DISCONNECTED/427275fcddef11ebaeaea25b204e9436/2da59d25-72e7-4052-afd3-f20fc8e6d0b7/DL20_Gen9.ahs"
        },
        {
            "name": "x-amz-algorithm",
            "value": "AWS4-HMAC-SHA256"
        },
        {
            "name": "x-amz-credential",
            "value": "ASIAZNSJDMBMQ5ZMIEMI/20250116/us-west-2/s3/aws4_request"
        },
        {
            "name": "x-amz-date",
            "value": "20250116T081435Z"
        },
        {
            "name": "x-amz-security-token",
            "value": "IQoJb3JpZ2luX2VjEEgaCXVzLXdlc3QtMiJGMEQCIGAynTcdUrAo/XYB4h6zBCQRzxN1LdMoAyz5I+QEGU8aAiBOQngRBr3Kuw8Z+eOkVunmy61Sh/r6fIGfIZ0p15bywyqDBQhBEAEaDDY0NzYxOTYzMzI0MSIMWqP4FtBVjcDfAKBcKuAE9OqhCRgz42iU1Htk1ELGvm51oKpiD6wy8/tnZi6LvHN+C18XGVkYc9LmImkWbZZOZQfduw9fAWbiOROMt/PXeC6g/fJwERo+vRSyuxs11O+IAGH+PTqc3HYvjrTVz6vmn2csSpyfIl7nGtLuWyAjYomdWfA0kMLkXfFPopBLJEA2Oo7FeQRUgmfKDpsjvnH4kUxkAWs7YECe5EYA1MqVgbqk/Rodg53EgHJjuOOAMLdl49iFpfh59YU4BdCNVctChqkRBlVG/Uv+UqoO4Rgv95HJyI6KzEnQs8sqMAU3xRFLZhjidL1zDx7ZUfdwASn/FPDrInwKfSSZqZ6oG+iJY3ITag8g4A1OP89hVjYV+BGg5hKvgwGpzjA4/Bj2Cg+IXHQcqPGp943XmISJDBBZ/TqQcgrgQ2pT/6s7CJdgsxcBJ7fXEbjp8GVBA9ETLDIvhGYglik7ZEIBpthwOw/LoaFMRSjS0HtKS/5xTOkmawe+vx8b+vg25wC1tzrdsAiBveAGd6VDtDAPddpJGIifclw566ZDmVlX/wxWrCvXU6g/V5Ktu1aoTpjaCLu0um9CRHB1HTX6zXJR1EFnFIPmL7tz3sjXfHVNDBBDt8tyCR80zXONOJi/EtRD+EMOHE1DqOCD400n9xF+xZ16FVAuICxmyeUCcrzBgfMVkF6sKUrSuhzQYy/knhfVxw2ODytGbITIduetIIs6AcXPltTBnpLo9bAcvzUJDZpUgdYv0C4t9p+Bja5NnBQmjSD6rsNULs+RSg+C+VX4CWGqzBpebUjD3Uc5sJGk4NLxo+KBDQ4w6/+ivAY6mwG1DjRD9TmRKB3wBx/ih8VsFlUcCR6pmNzR8LDZlzAJJHlyR1r6JhQDAkPMK4dRlMui2G27LonXGNWpg8/YN9aAFr/A5sOu2RmQKKfsMi9TI5IgvDrXK4ruOT0K4wQJTLRaEsIlJVvANK6/LcG/VLujkCm5GkTBLVb1uvuffkucGzJDjEyZ299M1NDvEnnXHFrl0xkMDzQiEptNXA=="
        },
        {
            "name": "policy",
            "value": "eyJleHBpcmF0aW9uIjogIjIwMjUtMDEtMTZUMDg6MjQ6MzVaIiwgImNvbmRpdGlvbnMiOiBbWyJjb250ZW50LWxlbmd0aC1yYW5nZSIsIDAsIDI2MjE0NDAwMF0sIHsiYnVja2V0IjogImRldi1ocGVjb21wdXRlc3VwcG9ydC11cy13ZXN0LTIifSwgeyJrZXkiOiAiQUhTX0RJU0NPTk5FQ1RFRC80MjcyNzVmY2RkZWYxMWViYWVhZWEyNWIyMDRlOTQzNi8yZGE1OWQyNS03MmU3LTQwNTItYWZkMy1mMjBmYzhlNmQwYjcvREwyMF9HZW45LmFocyJ9LCB7IngtYW16LWFsZ29yaXRobSI6ICJBV1M0LUhNQUMtU0hBMjU2In0sIHsieC1hbXotY3JlZGVudGlhbCI6ICJBU0lBWk5TSkRNQk1RNVpNSUVNSS8yMDI1MDExNi91cy13ZXN0LTIvczMvYXdzNF9yZXF1ZXN0In0sIHsieC1hbXotZGF0ZSI6ICIyMDI1MDExNlQwODE0MzVaIn0sIHsieC1hbXotc2VjdXJpdHktdG9rZW4iOiAiSVFvSmIzSnBaMmx1WDJWakVFZ2FDWFZ6TFhkbGMzUXRNaUpHTUVRQ0lHQXluVGNkVXJBby9YWUI0aDZ6QkNRUnp4TjFMZE1vQXl6NUkrUUVHVThhQWlCT1FuZ1JCcjNLdXc4WitlT2tWdW5teTYxU2gvcjZmSUdmSVowcDE1Ynl3eXFEQlFoQkVBRWFERFkwTnpZeE9UWXpNekkwTVNJTVdxUDRGdEJWamNEZkFLQmNLdUFFOU9xaENSZ3o0MmlVMUh0azFFTEd2bTUxb0twaUQ2d3k4L3RuWmk2THZITitDMThYR1ZrWWM5TG1JbWtXYlpaT1pRZmR1dzlmQVdiaU9ST010L1BYZUM2Zy9mSndFUm8rdlJTeXV4czExTytJQUdIK1BUcWMzSFl2anJUVno2dm1uMmNzU3B5ZklsN25HdEx1V3lBallvbWRXZkEwa01Ma1hmRlBvcEJMSkVBMk9vN0ZlUVJVZ21mS0Rwc2p2bkg0a1V4a0FXczdZRUNlNUVZQTFNcVZnYnFrL1JvZGc1M0VnSEpqdU9PQU1MZGw0OWlGcGZoNTlZVTRCZENOVmN0Q2hxa1JCbFZHL1V2K1Vxb080Umd2OTVISnlJNkt6RW5RczhzcU1BVTN4UkZMWmhqaWRMMXpEeDdaVWZkd0FTbi9GUERySW53S2ZTU1pxWjZvRytpSlkzSVRhZzhnNEExT1A4OWhWallWK0JHZzVoS3Znd0dwempBNC9CajJDZytJWEhRY3FQR3A5NDNYbUlTSkRCQlovVHFRY2dyZ1EycFQvNnM3Q0pkZ3N4Y0JKN2ZYRWJqcDhHVkJBOUVUTERJdmhHWWdsaWs3WkVJQnB0aHdPdy9Mb2FGTVJTalMwSHRLUy81eFRPa21hd2Urdng4Yit2ZzI1d0MxdHpyZHNBaUJ2ZUFHZDZWRHREQVBkZHBKR0lpZmNsdzU2NlpEbVZsWC93eFdyQ3ZYVTZnL1Y1S3R1MWFvVHBqYUNMdTB1bTlDUkhCMUhUWDZ6WEpSMUVGbkZJUG1MN3R6M3NqWGZIVk5EQkJEdDh0eUNSODB6WE9OT0ppL0V0UkQrRU1PSEUxRHFPQ0Q0MDBuOXhGK3haMTZGVkF1SUN4bXllVUNjcnpCZ2ZNVmtGNnNLVXJTdWh6UVl5L2tuaGZWeHcyT0R5dEdiSVRJZHVldElJczZBY1hQbHRUQm5wTG85YkFjdnpVSkRacFVnZFl2MEM0dDlwK0JqYTVObkJRbWpTRDZyc05VTHMrUlNnK0MrVlg0Q1dHcXpCcGViVWpEM1VjNXNKR2s0Tkx4bytLQkRRNHc2LytpdkFZNm13RzFEalJEOVRtUktCM3dCeC9paDhWc0ZsVWNDUjZwbU56UjhMRFpsekFKSkhseVIxcjZKaFFEQWtQTUs0ZFJsTXVpMkcyN0xvblhHTldwZzgvWU45YUFGci9BNXNPdTJSbVFLS2ZzTWk5VEk1SWd2RHJYSzRydU9UMEs0d1FKVExSYUVzSWxKVnZBTks2L0xjRy9WTHVqa0NtNUdrVEJMVmIxdXZ1ZmZrdWNHekpEakV5WjI5OU0xTkR2RW5uWEhGcmwweGtNRHpRaUVwdE5YQT09In1dfQ=="
        },
        {
            "name": "x-amz-signature",
            "value": "1fc2a080e55489f6e5ec0aac9e6da11990ea04a2f29aa2764e1e0f0246dbb703"
        }
    ]
}

Upload AHS file

note

Use the “parameters” list to create a pre-signed URL response to fill all the values in <>. It will form the upload command.

Copy

Copied

curl -i -F key=<key value> -F x-amz-algorithm=<algorithm value> -F x-amz-credential=<credential value> -F x-amz-date= <value> -F x-amz-security-token=<token value> -F policy=<policy value> -F x-amz-signature=<signature> -F file=@<filename> '<baseUrl value>'

An example curl command to upload an AHS file is shown below:

Copy

Copied

curl -i -F key=AHS_DISCONNECTED/427275fcddef11ebaeaea25b204e9436/72684583-59cf-4a81-b4c4-c4e586c8b0c1/upload_file_limit.ahs -F x-amz-algorithm=AWS4-HMAC-SHA256 -F x-amz-credential=ASIAZNSJDMBMWYRHACLJ/20250107/us-west-2/s3/aws4_request -F x-amz-date=20250107T094634Z -F x-amz-security-token=IQoJb3JpZ2luX2VjEHIaCXVzLXdlc3QtMiJIMEYCIQD+EB2Iqu1cy67R8K+sDhwCjjRoitcJWY7oZDOZ5Dmh6gIhAMCd0l9SGjOL0TWmBHn82IevIAzCl2r6F0quge2x3Ph9KoUFCFsQARoMNjQ3NjE5NjMzMjQxIgyUbBB1KigVNZp88agq4gQk7QuCSIudV2bgQ2UzP47NJx58KTC/bJ71wHdS9kBPpQqKFiHC3tsf6jsv4VNM0g+dUMsJdvOhk51zSqxTD5WL7YZpBI5SlYOOJ7FrVTNMc+aSxeTG6bHskiXTT6FTIiZve5+sa8FlEEIa0ZlR/ozoPHZks1b5vyEETkP1VUfgcxcpPuoD8aZqiMTgEkGZfdS2OhIsZRUWKy5Fdzo+nBUmOgv16MWcMV55q3gP5YfpVOCldORCciRqrYcUW2sXABdKHfddvRPI+W6nEveNHYSmpJ6n1UREcmfQLv/fBv4MdKHdELJlM0OwpduAJmPH+sbJN/XOaSP6AF5T/+hTEm2OZQ+cCtfsuC72N6ZtuhBvvviGquSjc35BGWXgkJeun3lgUUof/PUumD+q/fREceKF9qA1aRkWKZSMcmpIXfHPkf7y00pvrcTgCg5enARovbnOxwP+6aYXZ1zd+4yY0KmL8AD3xkUDgDVGvMHbOFmIbaPonFYb2TzOlABIOrD/aw66OHG9wfvpt9Z1JDhnT+hVJekbDg9NvwS0AD1ddNRqb/t1wAJq/fBqqxxSLjdiRDMgcyxYEQJ4uGvcaNecfIEJ3JCnihWShqfb2oDvi0dFzpt0F8R3qS4LovyyNrsCyuahPXzVNmJuD+a8If8OOf/XK/JEeHRjp2bO3ywMeefzotgHVOLhhytkpI2qZIKz/KleYEX2QTUYJZfVFWBddA2HxhCMxfxz+eglLQy7hXC+dPAmhtu0vZK5UwTODqspIMuG4KxbKoyd12v7Uc09RZ/VK0pyZsD7P6BxgqYHqxJuz3G0MPrv87sGOpkBnpVVn4B8y4W3FQOG2Gg3TZZ8RXl6LrWEnU1WbsTpSHpn2olTtqcpDj4t/sek6oRfzNPWMq6PBMuDhB7AY568BbrYslUAA/xDBCjJwq4owAUS11Z/vzyvfMHE664+erOuGod5XztoZ0NdHd5QtzZ8wT9Yq5Ee4GLTdHEuSwr8CeimlPFu+ZvOWgl0PqBs8advolCrXJKN0orA -F policy=eyJleHBpcmF0aW9uIjogIjIwMjUtMDEtMDdUMDk6NTY6MzRaIiwgImNvbmRpdGlvbnMiOiBbWyJjb250ZW50LWxlbmd0aC1yYW5nZSIsIDAsIDI2MjE0NDAwMF0sIHsiYnVja2V0IjogImRldi1ocGVjb21wdXRlc3VwcG9ydC11cy13ZXN0LTIifSwgeyJrZXkiOiAiQUhTX0RJU0NPTk5FQ1RFRC80MjcyNzVmY2RkZWYxMWViYWVhZWEyNWIyMDRlOTQzNi9jOTI0ZTc3MC1mNWYwLTQ2MDktYjFjYS05MjE5Mjc2ZDJhNWYvdXBsb2FkX2ZpbGVfcHJlc2lnbmVkX3Bvc3QuYWhzIn0sIHsieC1hbXotYWxnb3JpdGhtIjogIkFXUzQtSE1BQy1TSEEyNTYifSwgeyJ4LWFtei1jcmVkZW50aWFsIjogIkFTSUFaTlNKRE1CTVdZUkhBQ0xKLzIwMjUwMTA3L3VzLXdlc3QtMi9zMy9hd3M0X3JlcXVlc3QifSwgeyJ4LWFtei1kYXRlIjogIjIwMjUwMTA3VDA5NDYzNFoifSwgeyJ4LWFtei1zZWN1cml0eS10b2tlbiI6ICJJUW9KYjNKcFoybHVYMlZqRUhJYUNYVnpMWGRsYzNRdE1pSklNRVlDSVFEK0VCMklxdTFjeTY3UjhLK3NEaHdDampSb2l0Y0pXWTdvWkRPWjVEbWg2Z0loQU1DZDBsOVNHak9MMFRXbUJIbjgySWV2SUF6Q2wycjZGMHF1Z2UyeDNQaDlLb1VGQ0ZzUUFSb01OalEzTmpFNU5qTXpNalF4SWd5VWJCQjFLaWdWTlpwODhhZ3E0Z1FrN1F1Q1NJdWRWMmJnUTJVelA0N05KeDU4S1RDL2JKNzF3SGRTOWtCUHBRcUtGaUhDM3RzZjZqc3Y0Vk5NMGcrZFVNc0pkdk9oazUxelNxeFRENVdMN1lacEJJNVNsWU9PSjdGclZUTk1jK2FTeGVURzZiSHNraVhUVDZGVElpWnZlNStzYThGbEVFSWEwWmxSL296b1BIWmtzMWI1dnlFRVRrUDFWVWZnY3hjcFB1b0Q4YVpxaU1UZ0VrR1pmZFMyT2hJc1pSVVdLeTVGZHpvK25CVW1PZ3YxNk1XY01WNTVxM2dQNVlmcFZPQ2xkT1JDY2lScXJZY1VXMnNYQUJkS0hmZGR2UlBJK1c2bkV2ZU5IWVNtcEo2bjFVUkVjbWZRTHYvZkJ2NE1kS0hkRUxKbE0wT3dwZHVBSm1QSCtzYkpOL1hPYVNQNkFGNVQvK2hURW0yT1pRK2NDdGZzdUM3Mk42WnR1aEJ2dnZpR3F1U2pjMzVCR1dYZ2tKZXVuM2xnVVVvZi9QVXVtRCtxL2ZSRWNlS0Y5cUExYVJrV0taU01jbXBJWGZIUGtmN3kwMHB2cmNUZ0NnNWVuQVJvdmJuT3h3UCs2YVlYWjF6ZCs0eVkwS21MOEFEM3hrVURnRFZHdk1IYk9GbUliYVBvbkZZYjJUek9sQUJJT3JEL2F3NjZPSEc5d2Z2cHQ5WjFKRGhuVCtoVkpla2JEZzlOdndTMEFEMWRkTlJxYi90MXdBSnEvZkJxcXh4U0xqZGlSRE1nY3l4WUVRSjR1R3ZjYU5lY2ZJRUozSkNuaWhXU2hxZmIyb0R2aTBkRnpwdDBGOFIzcVM0TG92eXlOcnNDeXVhaFBYelZObUp1RCthOElmOE9PZi9YSy9KRWVIUmpwMmJPM3l3TWVlZnpvdGdIVk9MaGh5dGtwSTJxWklLei9LbGVZRVgyUVRVWUpaZlZGV0JkZEEySHhoQ014Znh6K2VnbExReTdoWEMrZFBBbWh0dTB2Wks1VXdUT0Rxc3BJTXVHNEt4YktveWQxMnY3VWMwOVJaL1ZLMHB5WnNEN1A2QnhncVlIcXhKdXozRzBNUHJ2ODdzR09wa0JucFZWbjRCOHk0VzNGUU9HMkdnM1RaWjhSWGw2THJXRW5VMVdic1RwU0hwbjJvbFR0cWNwRGo0dC9zZWs2b1Jmek5QV01xNlBCTXVEaEI3QVk1NjhCYnJZc2xVQUEveERCQ2pKd3E0b3dBVVMxMVovdnp5dmZNSEU2NjQrZXJPdUdvZDVYenRvWjBOZEhkNVF0elo4d1Q5WXE1RWU0R0xUZEhFdVN3cjhDZWltbFBGdStadk9XZ2wwUHFCczhhZHZvbENyWEpLTjBvckEifV19 -F x-amz-signature=ae66928f4062aac85ce5e43fbdeae392046f5375166ac08c1d70326dac4e781e -F file=@090887-K53+8899090887992537_FWUFailure.ahs 'https://dev-hpecomputesupport-us-west-2.s3.amazonaws.com/'

After the successful command execution, the AHS file is uploaded to the AWS S3 bucket.

AHS file upload failed

PATCH requests can be sent to /compute-ops-mgmt/v1beta1/ahs-files/{id} to update the status of AHS file.

Method	API	Property	JSON Type	Description	Required
PATCH	`/compute-ops-mgmt/v1beta1/ahs-files/{id}`	`status`	string	The status to be updated for an AHS file resource	Yes

A sample payload to create a patch request to update the parsing status of AHS file to ANALYSIS_FAILED is shown below:

Copy

Copied

{
    "parsingStatus": {
        "status": "ANALYSIS_FAILED"
    }
}

The following table summarizes the supported state transitions through PATCH request.

Existing Analysis State	Requested Analysis State	Supported
`ANALYSIS_PENDING`	`ANALYSIS_FAILED`	Yes
`ANALYSIS_IN_PROGRESS`	`ANALYSIS_FAILED`	Yes

note

During AHS analysis, once the file upload starts the initial status is set to ANALYSIS_PENDING. If the upload operation fails, the user should update the status from this initial state to the terminal state ANALYSIS_FAILED by using the above PATCH API call.

3. Parse AHS file

After uploading an AHS file to the pre-signed URL of the AWS S3 bucket, the user must send a request to parse the AHS file contents to get the required server details. To trigger the parse, send a POST request to the /compute-ops-mgmt/v1beta1/ahs-files/{id}/parse endpoint as shown below. The following property is used when creating a parse request:

Method	API	Property	JSON Type	Description	Required
POST	`/compute-ops-mgmt/v1beta1/ahs-files/{id}/parse`	`components`	string	Name of the component from AHS file which needs to be parsed	Yes

A sample payload to create a parse request to the uploaded AHS file is shown below:

Copy

Copied

{
    "components": "INVENTORY",
}

A sample response to a parse request is shown below:

200 OK

Wait for the AHS file parsing to complete

After the parse request, Compute Ops Management will start parsing the AHS file. During the parsing, the status will be shown as parsing in progress. The parsing status can be viewed by issuing a GET to the /compute-ops-mgmt/v1beta1/ahs-files endpoint with the correct path parameters for the task. The following table gives a few examples for viewing the parsing status.

Method	API	Property	Description
GET	`/compute-ops-mgmt/v1beta1/ahs-files/`	none	Get the parsing status of all the AHS files
GET	`/compute-ops-mgmt/v1beta1/ahs-files/{id}`	`id`	Get the parsing status of an AHS file with UUID of `id`
GET	`/compute-ops-mgmt/v1beta1/ahs-files?sort=parsingStatus%2FstatusModifiedAt+desc&limit=1`	none	Get the status of last parsed AHS file

The following table summarizes the possible parsing status values.

Status	JSON Type	Description
`ANALYSIS_PENDING`	String	The pre-signed URL is generated, but the file is not uploading or parsing
`ANALYSIS_IN_PROGRESS`	String	Uploaded AHS file parsing is in progress for the given component/s
`ANALYSIS_SUCCESS`	String	Uploaded AHS file parsing is successfully completed for the given component/s
`ANALYSIS_FAILED`	String	Uploaded AHS file parsing failed for the given component/s

A sample JSON response for a file that was parsed successfully from the GET call /compute-ops-mgmt/v1beta1/ahs-files/3f071e5c-07f0-4b45-a99a-ae084e71f5f0 is shown below:

Copy

Copied

{
    "id": "3f071e5c-07f0-4b45-a99a-ae084e71f5f0",
    "type": "compute-ops-mgmt/ahs-file",
    "generation": 6,
    "createdAt": "2025-02-27 07:32:18.684341Z",
    "updatedAt": "2025-02-27 07:32:30.573285Z",
    "resourceUri": "/compute-ops-mgmt/v1beta1/ahs-files/3f071e5c-07f0-4b45-a99a-ae084e71f5f0",
    "name": "HPE_MXQ2020JDN_20230911_GPU.ahs",
    "baseUrl": null,
    "parameters": [],
    "parsingStatus": {
        "status": "ANALYSIS_SUCCESS",
        "statusModifiedAt": "2025-02-27 07:32:30.536033Z",
        "statusReason": "",
        "errorCode": ""
    },
    "parsingResults": {
        "components": {
            "INVENTORY": {
               "csv": "MXQ2020JDN-20250227-0732-SERVER_INVENTORY.csv"
            }
        }
    },
    "hardware": {
        "productId": "R4G15A",
        "serialNumber": "MXQ2020JDN"
    }
}

A failure response sample from a GET call for getting the analysis status of a file identified by its UUID (id) /compute-ops-mgmt/v1beta1/ahs-files/7ffebeea-d6a6-4fe4-adbe-77d0a71ca691 is shown below:

Copy

Copied

{
    "id": "7ffebeea-d6a6-4fe4-adbe-77d0a71ca691",
    "type": "compute-ops-mgmt/ahs-file",
    "generation": 7,
    "createdAt": "2025-02-19 16:07:19.559038Z",
    "updatedAt": "2025-02-19 16:08:54.705760Z",
    "resourceUri": "/compute-ops-mgmt/v1beta1/ahs-files/7ffebeea-d6a6-4fe4-adbe-77d0a71ca691",
    "name": "HPE_AHS.ahs",
    "baseUrl": null,
    "parameters": [],
    "parsingStatus": {
        "status": "ANALYSIS_FAILED",
        "statusModifiedAt": "2025-02-19 16:08:54.668771Z",
        "statusReason": "due to unknown issue. Contact support if the problem persists (error code: AHSE-103).",
        "errorCode": "AHSE-103"
    },
    "parsingResults": {
        "components": {
            "INVENTORY": ""
        }
    },
    "hardware": {
        "productId": "KS000-100",
        "serialNumber": "VL9XXX0035"
    }
}

4. Download the parsed contents

To download the parsed server inventory CSV file, send a GET request to the /compute-ops-mgmt/v1beta1/ahs-files/{id}/download?filename={filename.csv} endpoint as specified below. Here, {id} represents the AHS file UUID from which we are trying to download the server information, and {filename.csv} is the parsing results inventory file name. The format of the CSV file name is server serial number-AHS file timestamp-upload time on local client.csv.

When you upload an AHS log file, the server inventory information in the resulting CSV file is derived from the latest bootlog present in the AHS log.

The server information CSV file contains the following set of data from the AHS:

Server inventory

General details, for example: Product name, serial number, Server ID, and power state.
Chassis
iLO
BIOS
Processor
Device inventory
Memory
Storage
Network
Power
Thermal
Firmware
Applications
Drivers
SD cards

Server logs

The last seven days from the following logs are included

Integrated Management Log
iLO Event Log
Security Log

Example download API call for the successfully parsed file is:/compute-ops-mgmt/v1beta1/ahs-files/f897360a-64b7-47bd-aac7-4e1f88cd3c9f/download?filename=MXQ2020JDN-20250226-1047-SERVER_INVENTORY.csv

A sample download API call response follows:

Copy

Copied

Product Name, ProLiant ML350 Gen10
Serial Number, MXQ2020JDN
ServerID, R4G15A:MXQ2020JDN
Date processed, 2025-02-26 10:47:44.619953+00:00 UTC
Power state, Not Available
Chassis
,ChassisType,FormFactor
,Unknown,4U
ILO
,ILOFirmware,ILOLicense
,iLO 5 v2.55p23 built on Oct 01 2021,iLO Advanced
BIOS
,BIOSVendor,BIOSVersion,BIOSReleaseDate
,,,
Processor
,None
Device
,FirmwareVersion,Location,Name,PartNumber,ProductVersion,SerialNumber,Status.Health
,4.11,Embedded RAID,HPE Smart Array P408i-a SR Gen10,804334-003,B,PZXNL0ARHFU0A9 ,Ok
,10.54.7,PCI-E Slot 1,HPE Ethernet 10Gb 2-port 562SFP+ Adapter,727055-B21,00,MYI1370M6L,Unknown
,0.70,Embedded Device,HPE Smart Storage Battery,875242-B21,01,6WQXP0GB2ER0UY,Ok
,1.2836.0,Embedded LOM,HPE Ethernet 1Gb 4-port 369i Adapter,,,,Unknown
,1.2836.0,PCI-E Slot 2,HP Ethernet 1Gb 4-port 366T Adapter,811546-B21,00,MYI151007F,Unknown
,N/A,PCI-E Slot 3,Empty slot 3,,,,Absent
,N/A,PCI-E Slot 4,Empty slot 4,,,,Absent
,90.04.96.00.01,PCI-E Slot 5,NVIDIA Tesla T4,900-2G183-0300-000,A1,1322821060318,Ok
,N/A,PCI-E Slot 6,Empty slot 6,,,,Absent
,90.04.96.00.01,PCI-E Slot 7,NVIDIA Tesla T4,900-2G183-0300-000,A1,1322821089515,Ok
,N/A,PCI-E Slot 8,Empty slot 8,,,,Absent
,2.5,Embedded Device,Embedded Video Controller,,,,Ok
Memory
,DeviceLocator,BaseModuleType,CapacityMiB,MemoryDeviceType,HPEPartNumber,Vendor,VendorPartNumber,OperatingSpeedMHz,MaximumSpeed,IsHPEMemory,HPESmartMemory,SerialNumber,CorrectableThresholdErrorCount,UnCorrectableThresholdErrorCount,Status.Health
,PROC 1 DIMM 3,RDIMM,65536,DDR4,P03053-0A1,Hynix,HMAA8GR7AJR4N-XN,2933 MHz,3200 MHz,No,Yes,848C3664,0,0,
,PROC 1 DIMM 5,RDIMM,65536,DDR4,P03053-0A1,Hynix,HMAA8GR7AJR4N-XN,2933 MHz,3200 MHz,No,Yes,848C3665,0,0,
,PROC 1 DIMM 8,RDIMM,65536,DDR4,P03053-0A1,Hynix,HMAA8GR7AJR4N-XN,2933 MHz,3200 MHz,No,Yes,848C3666,0,0,
,PROC 1 DIMM 10,RDIMM,65536,DDR4,P03053-0A1,Hynix,HMAA8GR7AJR4N-XN,2933 MHz,3200 MHz,No,Yes,848C3667,0,0,
,PROC 2 DIMM 3,RDIMM,65536,DDR4,P03053-0A1,Hynix,HMAA8GR7AJR4N-XN,2933 MHz,3200 MHz,No,Yes,848C362C,0,0,
,PROC 2 DIMM 5,RDIMM,65536,DDR4,P03053-0A1,Hynix,HMAA8GR7AJR4N-XN,2933 MHz,3200 MHz,No,Yes,848C362B,0,0,
,PROC 2 DIMM 8,RDIMM,65536,DDR4,P03053-0A1,Hynix,HMAA8GR7AJR4N-XN,2933 MHz,3200 MHz,No,Yes,848C3668,0,0,
,PROC 2 DIMM 10,RDIMM,65536,DDR4,P03053-0A1,Hynix,HMAA8GR7AJR4N-XN,2933 MHz,3200 MHz,No,Yes,848C3731,0,0,

note

Save the response from the download API call to a CSV file. Open the file to view the server information.