cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Pro Tip: Extension Framework 2.0 - Common Validation

AravindhanV
Participant

If you have adopted the Extension Framework 2.0 in your environment, then this post is for you. Here are some of the common issues encountered while creating the extensions, particularly with Custom DB query Extension, DB insights Extension (Oracle, PostgreSQL, MySQL, etc.), and SSL Certificates.

  • Successful Configuration but Undesired Results:

    • At times, when the configuration has been completed successfully and the status shows green (OK), we might think that everything is working fine. However, we wouldn't get the desired result because the extension execution was made successful, but the metric has not been populated due to some connectivity issue to the destination server (a most common case).

  • Custom DB Query Extension:

    • With the custom DB query extension, even though we can see that the connection has been established and polling has been finished, the query executed on the DB table might not give the correct value. This could be due to an incorrect value or type, or because the attribute for "Value" is not the same in the DB or in the query. So, it is necessary to validate the query.

  • Deployment of Custom DB Extension:

    • Ensure that the root certificate has been placed in ActiveGate and Credential Vault, and that the respective developer certificate is used for deployment.

  • Validation in Data Explorer:

    • If the custom DB has been configured and polling is successful, then validate in the "Data Explorer" with the key configured in the "Custom Extension Creator App".

  • Troubleshooting:

    • If you are still struggling to identify the issue, by default, use the path below to validate the extension logs against the AG where the extension is running for detailed exceptions or issues:

/var/lib/dynatrace/remotepluginmodule/log/extensions/datasources

  •  DB Insights Extension:
    • Validate the user privileges and restrictions before starting the implementation.

  • Support for Tech Versions:
    •  Validating the support of tech versions and OA versions is key to successful configuration.

Add your inputs as well which will ensure the Extension usage to the Finest 😊

Keep Exten(sion)d Dynatrace 👍

aravind
2 REPLIES 2

Danielm
Frequent Guest

Hi Aravin,

I think this is a very useful document for reference on the main issues I have noticed too.

Thanks.

prasanna_kl1984
Newcomer

Good insights on CUSTOM DB Query. Polling has been finished, and the query executed on the DB table; it is a general assumption that the query will work. However, we should also look into incorrect type while troubleshooting. 

Featured Posts