Connecting to the controller database w/mongodb 3.2

[Casey Marshall]

On Fri, May 13, 2016 at 10:52 AM, Horacio Duran <horacio.duran at canonical.com
> wrote:

> By connect I assume you mean to use the shell, for this you need the
> mongodb-org papa and install mongodb-org-shell, I am currently on the phone
> but as soon as I get to a computer I'll send you links
>
>
Well, for use case #1, yes, use the shell.

For use case #2, I'd be using github.com/dcu/mongodb_exporter, which uses
mgo.v2 and just needs a mongodb URI
<https://github.com/dcu/mongodb_exporter/blob/master/mongodb_exporter.go#L26>
.


> On Friday, 13 May 2016, Casey Marshall <casey.marshall at canonical.com>
> wrote:
>
>> I seem to be unable to connect to the Juju 2.0 controller database
>> lately. I'm thinking this might be related to the move to mongodb 3.2.
>>
>> Can someone in the know please share how to do this? While most users
>> should never, ever connect directly to the controller's database, I have
>> two good use cases for it:
>>
>> 1. It's sometimes necessary for debugging the state of a live controller.
>> 2. I'd like to instrument a controller's mongodb with prometheus.io, but
>> in order to do this, I need to derive the new connection info.
>>
>> Much thanks,
>> Casey
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160513/e4d16932/attachment.html>