Appdynamics / Appdynamics/AppDynamics.DEXTER

AppDynamics Dexter Configuration Issue

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

Description

Hi,

I have configured Dexter in my local system but Reports are not working properly. I have taken the logs and troubleshooting to find the issue.

**Error Logs**
2022-11-14 21:34:44.0445|Trace|AppDynamics.Dexter|13068|1|AppDynamics.Dexter.Program|AppDynamics DEXTER Version 21.8.0.0
2022-11-14 21:34:44.1531|Trace|AppDynamics.Dexter|13068|1|AppDynamics.Dexter.Program|Starting at local 2022-11-14T21:34:44.1529340+05:30/UTC 2022-11-14T16:04:44.1529386Z, Version=21.8.0.0, Parameters=
2022-11-14 21:34:44.1531|Trace|AppDynamics.Dexter|13068|1|AppDynamics.Dexter.Program|Timezone (UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi India Standard Time 05:30:00
2022-11-14 21:34:44.1531|Trace|AppDynamics.Dexter|13068|1|AppDynamics.Dexter.Program|Culture English (India)(en-IN), ShortDate=dd-MM-yyyy, ShortTime=HH:mm, All=dd-MM-yyyy;dd-MM-yy;d-M-yy;d.M.yy;yyyy-MM-dd;dd MMMM yyyy;d MMMM yyyy;dddd, d MMMM, yyyy;dd MMMM yyyy HH:mm;dd MMMM yyyy H:mm;dd MMMM yyyy hh:mm tt;d MMMM yyyy HH:mm;d MMMM yyyy H:mm;d MMMM yyyy hh:mm tt;dddd, d MMMM, yyyy HH:mm;dddd, d MMMM, yyyy H:mm;dddd, d MMMM, yyyy hh:mm tt;dd MMMM yyyy HH:mm:ss;dd MMMM yyyy H:mm:ss;dd MMMM yyyy h.mm.ss tt;dd MMMM yyyy hh:mm:ss tt;d MMMM yyyy HH:mm:ss;d MMMM yyyy H:mm:ss;d MMMM yyyy h.mm.ss tt;d MMMM yyyy hh:mm:ss tt;dddd, d MMMM, yyyy HH:mm:ss;dddd, d MMMM, yyyy H:mm:ss;dddd, d MMMM, yyyy h.mm.ss tt;dddd, d MMMM, yyyy hh:mm:ss tt;dd-MM-yyyy HH:mm;dd-MM-yyyy H:mm;dd-MM-yyyy hh:mm tt;dd-MM-yy HH:mm;dd-MM-yy H:mm;dd-MM-yy hh:mm tt;d-M-yy HH:mm;d-M-yy H:mm;d-M-yy hh:mm tt;d.M.yy HH:mm;d.M.yy H:mm;d.M.yy hh:mm tt;yyyy-MM-dd HH:mm;yyyy-MM-dd H:mm;yyyy-MM-dd hh:mm tt;dd-MM-yyyy HH:mm:ss;dd-MM-yyyy H:mm:ss;dd-MM-yyyy h.mm.ss tt;dd-MM-yyyy hh:mm:ss tt;dd-MM-yy HH:mm:ss;dd-MM-yy H:mm:ss;dd-MM-yy h.mm.ss tt;dd-MM-yy hh:mm:ss tt;d-M-yy HH:mm:ss;d-M-yy H:mm:ss;d-M-yy h.mm.ss tt;d-M-yy hh:mm:ss tt;d.M.yy HH:mm:ss;d.M.yy H:mm:ss;d.M.yy h.mm.ss tt;d.M.yy hh:mm:ss tt;yyyy-MM-dd HH:mm:ss;yyyy-MM-dd H:mm:ss;yyyy-MM-dd h.mm.ss tt;yyyy-MM-dd hh:mm:ss tt;d MMMM;d MMMM;yyyy'-'MM'-'dd'T'HH':'mm':'ss.fffffffK;yyyy'-'MM'-'dd'T'HH':'mm':'ss.fffffffK;ddd, dd MMM yyyy HH':'mm':'ss 'GMT';ddd, dd MMM yyyy HH':'mm':'ss 'GMT';yyyy'-'MM'-'dd'T'HH':'mm':'ss;HH:mm;H:mm;hh:mm tt;HH:mm:ss;H:mm:ss;h.mm.ss tt;hh:mm:ss tt;yyyy'-'MM'-'dd HH':'mm':'ss'Z';dd MMMM yyyy HH:mm:ss;dd MMMM yyyy H:mm:ss;dd MMMM yyyy h.mm.ss tt;dd MMMM yyyy hh:mm:ss tt;d MMMM yyyy HH:mm:ss;d MMMM yyyy H:mm:ss;d MMMM yyyy h.mm.ss tt;d MMMM yyyy hh:mm:ss tt;dddd, d MMMM, yyyy HH:mm:ss;dddd, d MM
[JObfile.txt](https://github.com/Appdynamics/AppDynamics.DEXTER/files/10005425/JObfile.txt)
MM, yyyy H:mm:ss;dddd, d MMMM, yyyy h.mm.ss tt;dddd, d MMMM, yyyy hh:mm:ss tt;MMMM, yyyy;MMMM, yyyy
2022-11-14 21:34:44.1531|Trace|AppDynamics.Dexter|13068|1|AppDynamics.Dexter.Program|Framework .NET Core 3.1.6
2022-11-14 21:34:44.1531|Trace|AppDynamics.Dexter|13068|1|AppDynamics.Dexter.Program|OS Architecture X64
2022-11-14 21:34:44.1531|Trace|AppDynamics.Dexter|13068|1|AppDynamics.Dexter.Program|OS Microsoft Windows 10.0.22000
2022-11-14 21:34:44.1531|Trace|AppDynamics.Dexter|13068|1|AppDynamics.Dexter.Program|Process Architecture X64
2022-11-14 21:34:44.1531|Trace|AppDynamics.Dexter|13068|1|AppDynamics.Dexter.Program|Number of Processors 8
2022-11-14 21:34:44.3176|Error|AppDynamics.Dexter|13068|1|AppDynamics.Dexter.Program|Could not parse command line arguments into ProgramOptions
2022-11-14 21:34:44.3176|Info|AppDynamics.Dexter|13068|1|AppDynamics.Dexter.Program|Application execution took 00:00:00.8330031 (833 ms)

Here i attached Job file also.
Many Thanks,
Sathis

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the AppDynamics.Dexter.Program entry point and its ProgramOptions parsing, then compare the attached JObfile.txt with the command-line arguments shown in the logs. Done means the configuration is accepted and reports run successfully, with a regression test or verified reproduction if the project provides one.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.