Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This article shows how to use Datadog with Smart ID Identity Manager.

<SMARTIDHOME>

In this article, <SMARTIDHOME> refers to /home/nexus, but this can be different depending on the setup.

Datadog is a cloud tool for monitoring. To get the applications data in there an Agent is required to run on the local machine.

In the SmartID package we have an example configuration for it in <SMARTIDHOME>/docker/compose/tools/datadog.

This is not ready to use by default and you should have knowledge about datadog before you start using it.


In <SMARTIDHOME>/docker/compose/tools/datadog/datadog.env you need to do some changed related to your environment in datadog.

Compare it to https://docs.datadoghq.com/agent/docker

We recommend to set DD_TAGS to identify your different environments.


To get some further information from the applications we provide an example for jmx. It is configured mainly in <SMARTIDHOME>/docker/compose/tools/datadog/conf.d/jmx.d/conf.yaml

This example is set up using https://docs.datadoghq.com/integrations/java/?tab=docker and https://github.com/DataDog/integrations-core/blob/master/tomcat/datadog_checks/tomcat/data/conf.yaml.example.

It's configured to connect to idm-operator:5000 without ssl. This port isn't listening by default, to enable it check <SMARTIDHOME>/docker/compose/identitymanager/operator/docker-compose.yml.

You can also setup ssl and authentication for this. As long as you know what containers you have running and don't adding a port mapping there shouldn't be an security issue by using it this way.

To provide an example of how to add additional attributes which are available as MBeans there is tomcat.connections.count and tomcat.thread.count.


  • No labels