Skip to content

Ben Morris

My feedback

2 results found

  1. 103 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Ben Morris commented  · 

    I think not having this support encourages the antipattern that your blog post talks about:
    https://www.mongodb.com/developer/languages/javascript/mongoose-versus-nodejs-driver/

    Specifically, the recommendation is to use database-level schema validation through the Mongo Node.js driver, rather than application-level models through an ODM like Mongoose.

    I'd like to use the recommendation but a prerequisite is terraform support to define the schema validation programmatically for our multiple projects and databases. As it stands, this need a lot of manual work which would take a lot of time and lead to inconsistencies/mistakes so it's a non starter for us unfortunately.

    Ben Morris supported this idea  · 
  2. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Atlas » Integrations  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Ben Morris commented  · 

    +1

    I've spent quite a bit of time today trying to get a v2 key working and ended up contacting Mongo support because I was getting inconsistent behaviour in the Atlas UI where I was trying to add a PagerDuty integration with a v2 key. This would work for the test, with a successful alert appearing in PagerDuty, but would fail when saving the integration. It gave the error: "Service Key PagerDuty service key must consist of 32 hexadecimal digits"

    I've been advised by Claudio in Mongo support that PagerDuty v2 keys are not supported they pointed me at this ticket. I don't think the documentation is clear that v2 keys aren't supported:

    https://www.mongodb.com/docs/atlas/tutorial/pagerduty-integration/#prerequisites just says "All new PagerDuty keys use their Events API v2. If you have an Events API v1 key, you can continue to use that key with Atlas." It could be clearer to explicitly say v2 isn't supported.

    UPDATE (Workaround): For my use case, the older Events API v1 was sufficient so I was able to add in an Events API v1 service integration in PagerDuty and then use this in the Atlas alert settings with the PagerDuty alert type.

    Ben Morris supported this idea  · 

Feedback and Knowledge Base