Documentation - monaco 2.0

[tatomir146]

Make sure all new features are well documented and covered by enough examples.

[tatomir146]

@kristofre we can consider to include the examples you mentioned today with this ticket?

[tatomir146]

Overriding complex values could not be done partially.

e.g. this kind of override will remove .complexThreshold.unit from the complexThreshold object:

parameters:
  threshold: 15
  complexThreshold:
    type: value
    value:
      amount: 15
      unit: sec

groupOverrides:
  - group: development
    override:
      parameters:
        complexThreshold:
          type: value
          value:
            amount: 20

[patrickpichler]

For this we should define something like an overrideStrategy flag which defines what to do with the values. Otherwise it will always merge the values.

The other question is, if it might make sense to split the value parameters into multiple parameter types such as scalar, list, map. Because some merge strategies only make sense on some of those types.

[tatomir146]

Regarding type: references You can reference to any type of properties, but it case you are referring to type: value it's not possible to reference subvalues. e.g.

...
    parameters:
      someMultiValues:
        type: value
        value:
          mike: lupus
          john: fabula

It is not allowed to map to the values of someMultiValues

    parameters:
      depParam:
        type: reference
        project: infrastructure
        api: alerting-profile
        config: some-config
        property: someMultiValues.mike
  

[heydenb]

When is V2 of monaco going GA? We need settings 2.0 API to describe log metrics based on log queries.

[kbocock-krg]

Hi not sure this is the right place, but I would like to see how we can lookup a cluster-->cloud application prior to creating a dashboard against it. The dashboard example we have needs the cloudapplication entityId.

[UnseenWizzard]

Hi not sure this is the right place, but I would like to see how we can lookup a cluster-->cloud application prior to creating a dashboard against it. The dashboard example we have needs the cloudapplication entityId.

Hi @kbocock-krg, not quite the right place - would have been fine to open a new discussion for this question I'd say :)

In general, there is currently no way to look-up and reference the IDs of existing entities that are not configured by monaco. This is planned as an upcoming feature though.

If the entity is configured via monaco you can reference its ID (https://dynatrace-oss.github.io/dynatrace-monitoring-as-code/configuration/yaml_config#referencing-other-configurations)

IIRC cloud applications are auto-discovered though, not configured right? In that case your only option for now is sadly to manually get the entity ID of the application (it is e.g. part of the URL when viewing an entity's UI page).