Thank you in advance. I've had a devil of a time trying to get this question answered by Atlassian support who only provide me with links and seem against talking to me on the phone.
We appear to have a premium license. Our Opsgenie application currently is set up tracking for one project with alert integration, alerts generation, incidents (manual and automated), etc. I have an incident list specific for this.
However, we have multiple programs which I would like to track. I don't necessarily want to set up alerts at this time, but I would like to have a separate incident list for each program which I can define/set up services for. How is this done? I would figure there's a way to set it up and toggle back and forth in Opsgenie between projects for their own incident lists, but I haven't found documentation to do this or if it can be. Any assistance is appreciated.
Hey @Doug Garcia ,
To create separate lists for each program you have defined a service for, you can use the search functionality in your Incidents menu:
Once you have defined that search for a particular Service you may go ahead and save that search for easy access and switching from the saved queries on the left side of the page:
This would then allow you to toggle back and forth between different Incident lists for each Service.
Hope that helps answer your query.
Best regards,
@Zeeshan, I appreciate the answer, but that was what I was worried about. Doing it by services and saving a search wouldn't work for me as we have several services already defined for a system level view of one product. What I'm thinking of doing is using a tag and create a Saved Search for the tag in manner similar to what you suggest. I was hoping there would be a different way, but does not appear so.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Doug Garcia ,
On the Incident list you can only create a search query for incident tags not service tags, so if your intended solution was to separate the services using tags and create a query on the Incidents list using those service tags, that will not work.
Instead, another suggestion would be to add the products' names in the Service names for example,
ProductA - Service 1
ProductA - Service 2
ProductB - Service 1
After that you can create a search query for ProductA the following way:
Best regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Zeeshan I appreciate the answer but that is definitely concerning. I inherited managing the incidents for our Opsgenie instance and how the team set things up before I arrived, they use Impacted Services as services for one product. Each service is basically a primary module which the system is dependent on. If I can't use tags in a Saved Search, that's not ideal if we intend to use this for tracking another Product or more in the future. But, I'll look into this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Doug Garcia
You're most welcome! Yes unfortunately Service tags cannot be used in Incidents' list search. If you like, I may go ahead and open up a Feature suggestion ticket for this to our Development team so that they may consider this for future implementation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Zeeshan
Thank you for the answers. I am a bit confused though. I just created a search based off a known tag and was able to save it just now. This is not ideal, but appears to be working as I would hope it would.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Doug Garcia ,
Those are the tags added on Incidents. Earlier we were discussing searching the Incident lists via the tags added on Services, which is not possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.