Versions Compared

Version Old Version 16 New Version 17
Changes made by

Meghali Deb Roy

Meghali Deb Roy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Compass can now integrate with powerful applications to bidirectionally sync alert data and streamline your IT operation workflows. In this chapter, learn all the ways to integrate Compass with your IT applications and products and use the integration framework to its fullest capability.

...

  •  Removed site-level content + hyperlink. Hope that’s fine?
Expand
titleLegends

🟡 Doubts in the content/links. Check with Shivi. {some specifically have JIRA settings written in the info section—that’s the only doubt} --- 11 items

🔵 Doubts about links only. Check with Shivi --- 16 items

🔶 Made necessary changes. Need to confirm with Shivi to get a (green star)

(green star) Successfully updated. No edits needed.

Other blue tags --- 8 items

Expand
titlePointers to incorporate

  • As Shivi suggested: if the code has any JSM or Opsgenie words/instance, ignore them (reuse the code) and mark the article as final >> (green star)

  • All hyperlinks currently pointing to JSM SAC should instead be pointing to the corresponding articles on this Compass microsite

    • Leave the Amazon URLs as they are

    Expand
    titleDiscrepancies/doubts

    1. The info section has to be updated. The one that starts with “If you're using the Free or Standard plan…“. Need an update from PM (Aditya Mani). Example

    2. Mention of OG/JSM in content (not code). Example

    3. Support links that go to Atlassian Support page. Do these need updates? Example

    4. Hyperlinks that go to Operations Help. What to update these to? example

    5. Hyperlinks that lead to this OG<>Solarwinds page. Example

    6. Hyperlinks that go to Github/other pages about JSM integration scripts or OG. Example1, Example2

    7. Hyperlinks that mention JSM or lead to pages that address JSM/OG. For example,

    8. Hyperlinks that lead to other SAC page under JSM. For example1, example2

    Expand
    titleDoubt #1

    I’ve identified two types of info sections in all the JSM original integration SAC.

    1. One is present for example in this SAC.
    This has been edited and updated as per your confirmation in our Slack thread to the following:

    Info

    Bidirectional integrations aren’t supported in the Standard plan. All the other integrations are supported at a team level in Standard.

    If you're using the Standard plan in Compass, you can add this integration only from your team’s operations page. Adding an integration from your team’s operations page makes your team the owner of the integration. This means Compass only assigns the alerts received through this integration to your team.

    2. The other one is present in this SAC. This content is different from the majority of other JSM SAC integration docs. I wanted to know whether I should use the same updated info panel content as present on top (“Bidirectional integrations aren’t supported in…“)?
    Or does this need to be a slightly different?