Im still struggling getting it working.
The latest schemas work, but its hard to debug.
UseCase: I want metric "com.dynatrace.extension.prometheus-nc-alertmanager.alert_state" to be available on the host screen.
As I understand from the F5 extension, the way to do this, is to relate the custom created entity to the Onagent host entity in the Topology section. Then in the Screen section call this relationship "isSameAs".
In the F5 example mapping is only done on ip_addresses, can this also be done on dt.entity.host?
As in my use case I only have attribute nc_alertmanager_host=dt.entity.host
An example of a extension, linking a metric to dt.entity.host and showing this in the host screen would be helpfull.
The provided examples are great, but hard to reverse engineer.
name: custom:dt.extension.prometheus-nc-alertmanager
version: 0.0.15
minDynatraceVersion: "1.259"
author:
name: xxx
#dashboards:
# - path: "dashboards/checkmk_network_devices.json"
metrics:
- key: com.dynatrace.extension.prometheus-nc-alertmanager.alert_state
metadata:
displayName: tn_nc_alertmanager_alert_state
description: tn_nc_alertmanager_alert_state
unit: Count
prometheus:
- group: nc_alertmanager metrics
interval:
minutes: 2
featureSet: all
subgroups:
- subgroup: nc_alertmanager_alert_state
dimensions:
- key: host
value: label:host
- key: event
value: label:event
- key: env
value: label:env
- key: severity
value: label:severity
- key: impact
value: label:impact
- key: description
value: label:description
- key: support_team
value: label:support
metrics:
- key: com.dynatrace.extension.prometheus-nc-alertmanager.alert_state
value: metric:NC_Alertmanager
type: gauge
featureSet: global
topology:
types:
- name: custom:dt_extension_prometheus_nc_alertmanager_host
displayName: nc_alertmanager Host
enabled: true
rules:
- idPattern: nc_alertmanager_{host}
sources:
- sourceType: Metrics
condition: $prefix(com.dynatrace.extension.prometheus-nc-alertmanager.alert_state)
attributes:
- pattern: '{host}'
key: nc_alertmanager_host
displayName: nc_alertmanager_host
- pattern: '{support_team}'
key: support_team
displayName: support_team
requiredDimensions: []
instanceNamePattern: '{host}'
relationships:
- sources:
- sourceType: Metrics
condition: $prefix(com.dynatrace.extension.prometheus-nc-alertmanager.alert_state)
fromType: "custom:dt_extension_prometheus_nc_alertmanager_host"
toType: host
typeOfRelation: SAME_AS
- sources:
- sourceType: Entities
mappingRules:
- sourceProperty: nc_alertmanager_host
sourceTransformation: To lower case
destinationProperty: dt.entity.host
destinationTransformation: To lower case
fromType: custom:dt_extension_prometheus_nc_alertmanager_host
typeOfRelation: SAME_AS
toType: host
screens:
- entityType: HOST
detailsInjections:
- type: CHART_GROUP
key: host-ncalertmanager-alerts
conditions:
- relatedEntity|entitySelectorTemplate=type(custom:dt_extension_prometheus_nc_alertmanager_host),fromRelationships.isSameAs($(entityConditions))
chartsCards:
- key: "host-ncalertmanager-alerts"
displayName: "NC Alertmanager Alerts"
numberOfVisibleCharts: 1
charts:
- displayName: "NC Alertmanager alerts"
visualizationType: GRAPH_CHART
graphChartConfig:
stacked: false
metrics:
- metricSelector: "com.dynatrace.extension.prometheus-nc-alertmanager.alert_state:SplitBy(description)"
visualization:
displayName: Status
The Graph_chart is added to the host screen, the metric is just not related.
Please help.
I fixed it like this:
topology:
types:
- name: custom:dt_extension_prometheus_nc_alertmanager_host
displayName: nc_alertmanager Host
enabled: true
rules:
- idPattern: nc_alertmanager_{host}
sources:
- sourceType: Metrics
condition: $prefix(com.dynatrace.extension.prometheus-nc-alertmanager.alert_state)
attributes:
- pattern: "{host}"
key: nc_alertmanager_host
displayName: nc_alertmanager_host
- pattern: "{support_team}"
key: support_team
displayName: support_team
requiredDimensions: []
instanceNamePattern: "{host}"
relationships:
- sources:
- sourceType: Entities
mappingRules:
- sourceProperty: nc_alertmanager_host
sourceTransformation: To lower case
destinationProperty: displayName
destinationTransformation: To lower case
fromType: custom:dt_extension_prometheus_nc_alertmanager_host
typeOfRelation: SAME_AS
toType: host
screens:
- entityType: HOST
detailsInjections:
- type: CHART_GROUP
key: host-ncalertmanager-alerts
conditions:
- relatedEntity|entitySelectorTemplate=type(custom:dt_extension_prometheus_nc_alertmanager_host),fromRelationships.isSameAs($(entityConditions))
chartsCards:
- key: "host-ncalertmanager-alerts"
displayName: "NC Alertmanager Alerts"
numberOfVisibleCharts: 1
charts:
- displayName: "NC Alertmanager alerts"
visualizationType: GRAPH_CHART
graphChartConfig:
stacked: false
metrics:
- metricSelector: "com.dynatrace.extension.prometheus-nc-alertmanager.alert_state:filter(in(\"dt.entity.custom:dt_extension_prometheus_nc_alertmanager_host\",entitySelector(\"type(custom:dt_extension_prometheus_nc_alertmanager_host),fromRelationships.isSameAs($(entityConditions))\"))):splitBy(\"description\")"
visualization:
displayName: Status
Result:
To check if your entities are linked, you need too querry the API /api/v2/entities/CUSTOM_DEVICE-******
And then you should see something like:
"fromRelationships": {
"isSameAs": [
{
"id": "HOST-*****",
"type": "HOST"
}
]
}
Featured Posts
