Appdynamics / Appdynamics/AppDynamics.DEXTER

Cannot see account node property

Open
#105 2 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C#
Stars
85
Forks
1
PR merge metrics
No merged PRs in 30d

Description

The controller setting node.retention.period is the time (in hours) after which a node that has lost contact with the controller is marked deleted. DEXTER reports this setting in the Configuration report.

Typically for SaaS controller this setting is made at the account level. For background, see https://confluence.corp.appdynamics.com/pages/viewpage.action?pageId=10352198

I defined node.retention.period on a test controller as an account property set to 24. I verified that property was in place:
mysql> select * from account_configuration_property where name like '%node%' ;
+--------------------------+-----------------------+-------+
| account_configuration_id | name | value |
+--------------------------+-----------------------+-------+
| 2 | node.retention.period | 24 |
+--------------------------+-----------------------+-------+
1 row in set (0.00 sec)

mysql> quit

I ran a report against the test controller using the attached job file. It showed the controller setting node.retention.period set to default 500; it did not show the account property.

I have not found an API for account properties; so I'm unsure if this enhancement can be implemented. I believe that DEXTER should provide visibility for all account properties: if there is no API, we should request one via an IDEA.

[dskeen04271100.json.txt](https://github.com/Appdynamics/AppDynamics.DEXTER/files/4541373/dskeen04271100.json.txt)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the attached dskeen04271100.json.txt job file and compare its Configuration report output with the account_configuration_property row shown in the issue. Determine whether an API exposes account properties; done means the report visibly includes account-level node.retention.period, or the issue records that an API request is required.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, mysql
Domain
api, backend, data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.