We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
JSON shape defined for inventory on the public docs: https://docs.newrelic.com/docs/create-integrations/infrastructure-integrations-sdk/specifications/host-integration-executable-file-json-specifications#inventory
mentions:
inventory data type is a hash of one or more JSON sub-objects
And https://docs.newrelic.com/docs/create-integrations/infrastructure-integrations-sdk/specifications/host-integration-executable-file-json-specifications#inventory
Values may either be a scalar type (string or number) or another hash object of key/values.
But turns out there are some issues:
Agent doesn't support several embedded layers: see test failing at Fix: nested inventory items #176
Platform ingest all kind of inventory data with success, but later on data is not showned.
And there's a UI issue as well:
UI is misleading as nested objects aren't reflected: https://docs.newrelic.com/docs/infrastructure/infrastructure-ui-pages/infra-ui-pages/infrastructure-inventory-page-search-your-entire-infrastructure
The inventory item name is comprised of three elements
And those not even nested keys, they are actually: inventory source split in 2 + 1 single key
Agent should be able to properly handle nested inventory items.
Consider inventory public API docs, so expectations might be made on how clients should behave.
Inventory UI might be required to be updated as well to represent nested key/value pair items.
See above PR failing test. It's payload could be used to reproduce the 3 mentioned issues.
Integration returning nested objects for inventory (test attached payload).
The text was updated successfully, but these errors were encountered:
category/source/key1/.../keyN
Sorry, something went wrong.
varas
Successfully merging a pull request may close this issue.
Description
JSON shape defined for inventory on the public docs:
https://docs.newrelic.com/docs/create-integrations/infrastructure-integrations-sdk/specifications/host-integration-executable-file-json-specifications#inventory
mentions:
And https://docs.newrelic.com/docs/create-integrations/infrastructure-integrations-sdk/specifications/host-integration-executable-file-json-specifications#inventory
But turns out there are some issues:
Agent doesn't support several embedded layers: see test failing at Fix: nested inventory items #176
Platform ingest all kind of inventory data with success, but later on data is not showned.
And there's a UI issue as well:
UI is misleading as nested objects aren't reflected: https://docs.newrelic.com/docs/infrastructure/infrastructure-ui-pages/infra-ui-pages/infrastructure-inventory-page-search-your-entire-infrastructure
And those not even nested keys, they are actually: inventory source split in 2 + 1 single key
Expected Behavior
Agent should be able to properly handle nested inventory items.
Consider inventory public API docs, so expectations might be made on how clients should behave.
Inventory UI might be required to be updated as well to represent nested key/value pair items.
Steps to Reproduce
See above PR failing test. It's payload could be used to reproduce the 3 mentioned issues.
Your Environment
Integration returning nested objects for inventory (test attached payload).
The text was updated successfully, but these errors were encountered: