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

Prometheus Extension 2.0 best practices

SjoerdB
Advisor

Hi fellow Dynatracers,

I am currently writing an extension for scraping a prometheus endpoint of an appliance. This is a virtual appliance that is under update control of the supplier.

Coding

  • What is best practice for the extension name (e.g. biz.ictcore.<suppliername>.<supplierProductname>) to use safe namespaces (ictcore.biz is my domain)?
  • What is best practice for the metrics naming (<suppliername>.<supplierProductname>.<original prometheusMetricname>), to avoid clashes?
  • This specific Prometheus reply also contains some static values, like a build_info metric. How could I put this information into attributes for my topology, so that it gets visible in the properties (like I already put in some other info in properties)?
    # HELP node_exporter_build_info A metric with a constant '1' value labeled by version, revision, branch, goversion from which node_exporter was built, and the goos and goarch for the build.

     

example for <suppliername>.<supplierProductname> could be paloalto.cortexxdr or f5.bigip ... etc.

Dynatrace Certified Professional
0 REPLIES 0

Featured Posts