matthewponzio

Oh..never mind, I found it…under HTTP-Based monitoring — http://localhost:8080/metrics/prometheus Now just need to figure out how to authenticate to it properly.

Ah, cool. So I’m trying to configure prometheus monitoring, but I can’t seem to find the prometheus endpoint url for OpenDJ in the docs? I tried http://localhost:8080/json/metrics/prometheus and http://localhost/json/metrics/prometheus, but no good:

prometheus (2.0.0)
------------------
Instance ID: prometheus:a054d854bd81b5a3…[Read more]

Hey, looks like I don’t have access to https://ea.forgerock.com/docs..

Forbidden
You don't have permission to access /docs/ds/monitoring-guide/chap-monitoring.html on this server.

Could be because my Backstage account isn’t linked to a paid Support Agreement? The company I’m working at does have a support agreement, but I’m a consultant, and…[Read more]

Wow, awesome. Thanks so much for the diligent follow up! So yeah, looking the JMX MBeans from my DJ 3.5 servers, I see that ds-backend-entry-count was java.lang.String.

I’ll definitely take a look at the docs you mentioned in your PS. Thanks again!!

I’ve shortened the output as much as possible, but this is the list of all the JMX Attributes/MBeans that the Datadog agent can see. It’s quite a lot, so that’s why I’m fairly sure my permissions and configuration are correct…but conspicuously missing from this list are ds-mon-current-delay and ds-mon-backend-entry-count

Rdn1=cn-monitor,Rdn2=cn…[Read more]

Hi Ludo, thanks for the reply. Yes, we most definitely have the correct permissions. We’re using cn=Directory Manager user and we also are using the correct service URL.

As I said, I am able to see most all of the JMX attributes/metrics under cn=montior, so I’m all but certain we have the correct permissions and JMX URL config.

The Datadog…[Read more]

And Dom…thanks for getting that KB article updated so fast! Looks perfect! Cheers.

Oh…just saw in my email…Got a message from Dom Reed. For some reason he didn’t post here. Here is his message:

Hi Matthew

Thank you for your feedback. You are correct, this has changed in DS 6. Appologies this was missed when I updated articles for DS 6 – I have updated it now and republished. I will also update any related articles.

Many…

[Read more]

Hey, thanks for the reply, but I’m not sure I follow. Read privileges to the monitoring data doesn’t seem to be the problem. I’m not getting any kind of access denied error. The problem is that the baseDN changed from “cn=userRoot Backend,cn=monitor” to “ds-cfg-backend-id=userRoot,cn=backends,cn=monitor”.

Bad copy/paste for the original DJ 3.5 ldapsearch command at the top of my post…

It should be:
ldapsearch -h <hostname> -p <port> -D "cn=Directory Manager" -w <password> -b "cn=userRoot Backend,cn=monitor" -s sub "(objectClass=*)"

Hi Ludo, thanks so much for the reply. Sorry, totally forgot to include the version…it’s 3.5. I’m hopeful that we will be able to be upgrade to 6 sometime fairly soon, so this may be a moot point indeed. I did see the note in the docs that missing_changes was deprecated in v6. Probably not worth pursuing a resolution at this stage then,…[Read more]