Snowflake Extension does not produce appropriate vertices
search cancel

Snowflake Extension does not produce appropriate vertices

book

Article ID: 387475

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Snowflake monitoring APMIA extension did not appear to create vertices in our latest deployment for the CAT IoT Demo -- it would be useful to have 3 types of vertices created:

SNOWFLAKE_SERVICE -- would include client endpoint, service location (aws, gcp, azure  etc) and service availabilty metrics.
SNOWFLAKE_WAREHOUSE_ACCOUNT -- it's best to split query execution by account + warehouse for usage in our service definitions
SNOWFLAKE_WAREHOUSE -- would have usage, credits, storage and other warehouse specific metrics

upstream applications should be topologically connected to a SNOWFLAKE_WAREHOUSE_ACCOUNT on the APPLICATION LAYER, SNOWFLAKE_SERVICE and SNOWFLAKE_WAREHOUSE on the INFRASTRUCTURE LAYER

remember, it is common to have a single SNOWFLAKE_SERVICE endpoints with DEV/QA/TEST/PROD Warehouses.

It is also common to have snowflake accounts that talk to multiple warehouses -- which we need to differentiate.

It is less common, but some customers will have both AWS + AZURE SNOWFLAKE_SERVICES or multiple SNOWFLAKE_SERVICES, with the same warehouse names, and potentially the same account names. 

There is also a typo in storage here:

Environment

Any DX APM Infrastructure Agent release.

Resolution

With current Snowflake extension we only create vertex for DB(master and slave) with accound admin. We are not creating vertex for SNOWFLAKE_SERVICE,WAREHOSE and also they need the warehouse_account on application layer.

This is a ER.