Appdynamics / Appdynamics/AppDynamics.DEXTER

Enhancement Request: Remove the Input section from the job file

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

Description

I would like it if the job file only contained the target and output section. Why do I have to specify an input section? Shouldn't Dexter be able to figure that out based on the reports I've requested?

I've spent many hours running and waiting for Dexter reports and it was probably spending the time querying data I didn't need.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing how Dexter reads the job file's input, target, and output sections, then inspect how requested reports identify the data they need. Done means the input section can be removed without losing required data selection and reports avoid querying unneeded data, with tests covering the new job-file behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.