youngmon/atlassian-qna huggingface dataset:
Status page - question on page view for private status page
Asked by Darshan Kumar:

<https://www.atlassian.com/software/statuspage/pricing?tab=private>

Wanted to know if the private page view with google auth login is limited to each subscription how this works:  
"any" number of people can view or is this limited to 50 with the private page

Is the page view limited to 50/month for 79$?

Please help me to understand more on using the google auth for private login.  
ref <https://support.atlassian.com/statuspage/docs/authenticate-with-google/>  
is it that any user with google auth (with domain specified) can login or is it limited to 50 users page view. how it works.


Answers:
author: Nikola
body: Hi Darshan,

Thanks for reaching out to Statuspage team.  
The main purpose of a Private page is to make it visible only to authenticated users. It allows you to communicate privately with page viewers who can access your page via internal authentication tools.

##### Private page plans {#toc-hId-1870379449}

In regards to your question about pricing plans, Starter plan will allow you to have up to 5 Team Members (Statuspage admins that can create/update incidents and components, as well as add new users), and up to 50 Employees, which are the users that will be able to authenticate and view your Statuspage.

##### Google auth {#toc-hId-62924986}

Google auth is meant to be used by the organizations, so you will need to specify a domain, or a list of domains, that will have the permission to authenticate to your Statuspage. Once you enable it, the users will authenticate using their Google credentials associated with the domain you have defined.

I hope this cleared the doubts you had Darshan. Let me know if there's anything else you'd like to know.

Cheers,
How do you decide on what components to show on your status page?
Asked by Michelle Bautista:

We're trying to identify what components to show on the Status page and we're seem to be stuck on identifying what make sense. Im hoping to hear best practices or how you decide on what to show on your page.


Answers:
author: Nick Coates
body: Hey [@Michelle Bautista](/t5/user/viewprofilepage/user-id/3984340) , welcome to the Atlassian Community!

I'm from Broadcom, a long-term Statuspage customer! I just wanted to draw on what [@Jake Bartlett](/t5/user/viewprofilepage/user-id/998391) has provided and give you an example on how we decide what components we share across our 13+ pages.

As most of our products are Saas/Cloud and vary in how they are configured, we have two types of structure we typically follow:

* Customers provisioned in regions or data center's, so our structure is to have the Product name as a group/parent component and then underneath we have the regions (example: our [Symantec Email Security](https://email-security.status.broadcom.com/) page shows our .cloud product split into regions)
* Customer-facing components that make up the platform of that product for example our [Cloud Workload Assurance](https://information-protection.status.broadcom.com/) product has a customer facing portal and a provisioning API that our customers use so we structured our components.

I always recommend thinking about your products/platform and what issues your customers may face then structure the components on what customers will know. Always make sure your components make sense to your customers.

You can check out our Statuspages [here](https://status.broadcom.com/) which hopefully gives you some ideas.

Cheers,  
Nick Coates  
Product Owner - Service Status, Broadcom Inc.


author: Jake Bartlett
body: Hi [@Michelle Bautista](/t5/user/viewprofilepage/user-id/3984340) thanks for the question! The best way to determine what components to include on your status page is to consider what important services, features, or products your customers depend on. What items / services have had outages or performance issues in the past? What are the most important parts of your service to your customers?

For example, you might have a mobile app, a website, a help center, and an API -- all of those could be components. You could even drill in further and add individual features as components (e.g. email sending, notifications, file uploads). Here are a couple links with additional information:

* [Show service status with components](https://support.atlassian.com/statuspage/docs/show-service-status-with-components/) (see link to video)
* [What is a component?](https://support.atlassian.com/statuspage/docs/what-is-a-component/)(see example status pages)

We recommend keeping components to a manageable number. Start small and add more as needed. You can also use [component groups](https://support.atlassian.com/statuspage/docs/create-a-component-group/) to keep things organized.
How can I widen my banner and make it clickable
Asked by Naxey:

I want my banner to be the entirety of the screen and make it a link that redirects to my webpage. It would also be neat to remove the small gray banner with the name on it  

my page is [https://siriusbot.statuspage.io](https://siriusbot.statuspage.io/#)

but id like to have it more like this<https://status.discord.com/>


Answers:
author: Nick Coates
body: Hi Naexy,

Welcome to the Atlassian Community! I'm Nick from the Broadcom team, long-term Statuspage customer.

You will need to use Customization for this and use CSS to modify the div that controls the banner. Customization is on higher plans and requires custom domains.

If you're going to upgrade + add custom domain, you'll want to either make the width to 100%/100vw on masthead-container or cover-image-container, not sure which one but playing around with the CSS will work.

Hope this helps!  

<br />

Cheers,  
Nick Coates  
Product Owner - Service Status, Broadcom Inc.
{"error":"incident is missing"} when using PATCH or PUT to update an incident
Asked by Norman Khine:

Hello,

When I try to submit a PATCH or PUT request to update an incident, I get:

```
{"error":"incident is missing"} 
```

Here is my request:

```
curl --location --request PATCH 'https://api.statuspage.io/v1/pages/xxxx/incidents/lf7****nf2?api_key=xxx' \
--header 'Content-Type: application/json' \
--data-raw '{
"incident": "Requests Failed (500)",
"status": "identified"
}'
```

I have also tried with Authorization: Oauth \<api-key\> approach

I am able to create an incident and am also able to list them, so I am unsure what is going on.

I am following <https://developer.statuspage.io/#operation/putPagesPageIdIncidentsIncidentId> and <https://developer.statuspage.io/#operation/patchPagesPageIdIncidentsIncidentId>

What am I missing?

Any advice is much appreciated


Answers:
author: Norman Khine
body: i need to use <https://doers.statuspage.io/api/v1/> methods


author: Zach
body: Hey Norman

Yeah, you're going to need to wrap everything in an incident container. So your call would need to look similar to the example shown on doers.statuspage.io -

```
curl https://api.statuspage.io/v1/pages/{page_id}/incidents.json \
-H "Authorization: OAuth **************" \
-X PATCH \
-d "incident[name]=Requests Failed (500)" \
-d "incident[status]=identified" \
-d "incident[body]=Sample update" \
-d "incident[component_ids][]=yxrqcr0kc3hx" \
```
Incident History Limit
Asked by gtiguy92:

We are thinking of opening a public status page and were wondering if it's possible to limit the number of days worth of incident history that is publicly visible?


Answers:
author: Nick Coates
body: Hi! Welcome to the Atlassian Community. Nick from the Broadcom team, long-time Statuspage customer!

There isn't an out of the box configuration to do this and I believe you can't do this via customization either. This is for both Incident History and Uptime.

Thanks,  
Nick Coates  
Product Owner - Service Status, Broadcom.
My api key is when i gen it it does not show the api key
Asked by Shawn Hamby:

also when i put this code in i get a error

CODE:

1. var http = require('http');

2.

3. // The following 4 are the actual values that pertain to your account and this specific metric.

4. var apiKey = 'your-api-key-goes-here';

5. var pageId = 'ktnkzq1wp4wc';

6. var metricId = 'ly0m7lhl7gj0';

7. var apiBase = '<https://api.statuspage.io/v1>';

8.

9. var url = apiBase + '/pages/' + pageId + '/metrics/' + metricId + '/data.json';

10. var authHeader = { 'Authorization': 'OAuth ' + apiKey };

11. var options = { method: 'POST', headers: authHeader };

12.

13. // Need at least 1 data point for every 5 minutes.

14. // Submit random data for the whole day.

15. var totalPoints = 60 / 5 \* 24;

16. var epochInSeconds = Math.floor(new Date() / 1000);

17.

18. // This function gets called every second.

19. function submit(count) {

20. count = count + 1;

21.

22. if(count \> totalPoints) return;

23.

24. var currentTimestamp = epochInSeconds - (count - 1) \* 5 \* 60;

25. var randomValue = Math.floor(Math.random() \* 1000);

26.

27. var data = {

28. timestamp: currentTimestamp,

29. value: randomValue,

30. };

31.

32. var request = http.request(url, options, function (res) {

33. res.on('data', function () {

34. console.log('Submitted point ' + count + ' of ' + totalPoints);

35. });

36. res.on('end', function() {

37. setTimeout(function() { submit(count); }, 1000);

38. });

39. });

40.

41. request.end(JSON.stringify({ data: data }));

42. }

43.

44. // Initial call to start submitting data.

45. submit(0);

ERROR:
> working  
> working  
> _http_client.js:152  
> throw new ERR_INVALID_PROTOCOL(protocol, expectedProtocol);  
> \^
>
> TypeError \[ERR_INVALID_PROTOCOL\]: Protocol "https:" not supported. Expected "http:"  
> at new ClientRequest (_http_client.js:152:11)  
> at Object.request (http.js:46:10)  
> at submit (C:\\Users\\ShawnHamby\\Desktop\\John\\APi.js:33:22)  
> at Object.\<anonymous\> (C:\\Users\\ShawnHamby\\Desktop\\John\\APi.js:47:1)  
> at Module._compile (internal/modules/cjs/loader.js:1138:30)  
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)  
> at Module.load (internal/modules/cjs/loader.js:986:32)  
> at Function.Module._load (internal/modules/cjs/loader.js:879:14)  
> at Function.executeUserEntryPoint \[as runMain\] (internal/modules/run_main.js:71:12)  
> at internal/main/run_main_module.js:17:47 {  
> code: 'ERR_INVALID_PROTOCOL'  
> }


Answers:
author: Nick Coates
body: Hi Shawn,

I think this is a Node (this looks like NodeJS, correct if I'm wrong) error where it's using the https protocol in the apiBase parameter and is expecting http instead.

***TypeError \[ERR_INVALID_PROTOCOL\]: Protocol "https:" not supported. Expected "http:"***

Thanks,  
Nick Coates  
Product Owner - Service Status, Broadcom.
{"error":"incident[components] is invalid"} (PHP)
Asked by Kmeleon:

I did more than 10 ways to put the incident connected with the component but no one works correctly .

**Structured array:**

$array = array();  
foreach ($components as $component)  
{  
$array\[$component\['id'\]\] = $components_status;  
}  
$postparams = array();  
$postparams\["incident\[components\]"\] = json_encode($array);  
foreach ($components as $component)

{  
$cid = $component\['id'\];  
$postparams\["incident\[components\]\[$cid\]"\] = $components_status;  
}

My output is similar to the API documentation but not work

Array  
(  
\[incident\[component_ids\]\] =\> \[".....3j0qxc",".....38ds4m",".....h59d9"\]  
\[incident\[components\]\] =\> {".....j0qxc":"partial_outage",",,,,,,8ds4m":"partial_outage",".....7h59d9":"partial_outage"}  
)

The incident always is created with no component associated, and I need make this relationship under statuspage.

I shared the function of my class here :

<https://pastebin.com/TmyZHZbJ>

Any idea?


Answers:
author: Kmeleon
body: Finally I found a way, here the correct way to connect the incident with a component:

$this-\>param\["incident\[component_ids\]"\] = '\["....k38ds4m"\]';  
$this-\>param\["incident\[components\]\[.....k38ds4m\]"\] = self::COMPONENT_STATUS_PARTIAL_OUTAGE;


author: Kmeleon
body: Did other tests and nothing...

Anyone can help me ???

{"error":"incident\[components\] is invalid"}  
Array  
(  
\[incident\[name\]\] =\> Teste 14:39:26-9783  
\[incident\[body\]\] =\> Em 14:39:26 foi registrado o erro 160 na rotina Objeto.Teste()  
\[incident\[status\]\] =\> identified  
\[incident\[impact_override\]\] =\> major  
\[incident\[component_ids\]\] =\> \[".......hf4pq","......7h59d9"\]  
\[incident\[components\]\] =\> {"......hf4pq":"partial_outage",".....7h59d9":"partial_outage"}  
)


Tags: incident

php
Creating a past incident
Asked by Dougal Guppy:

Hi -

I've created a previous incident in StatusPage but there's not an option to select the resolution date, which was a week later.

Is there another way I can represent this incident which spanned over more than a day?

Thanks,  
Dougal


Answers:
author: Zach
body: Hey Dougal!

You can create a new incident (make sure the 'send notifications' option is disabled!) then immediately go back in to resolve the incident similar to the earlier mentioned answer.

The benefit of creating the incident, and then resolving it, is that you can edit the time it was reported, as well as the time of the resolution update. That way you can have it spanning however long you'd like.


author: Kmeleon
body: I did test too, probably the way of close the incident is tagging it as **resolved**

But the event's date/time cannot be changed , so when you send the update via api probably this will be considered the resolution date/time.
Unable to create component in the API
Asked by Patrick Rutledge:

I thought I was following the API documentation correctly but I am unable to create a component via the statuspage.io API.

Here is the payload I am sending via POST [https://api.statuspage.io/v1/pages/\<mypageID\>/components]()

{'component': {'name': 'placeholder', 'showcase': False, 'only_show_if_degraded': False, 'description': 'placeholder', 'status': 'operational'}}

I get back:

{'error': 'component is missing'}

What am I doing wrong here?


Answers:
author: Hana Ku?erov?
body: Hi [@Patrick Rutledge](/t5/user/viewprofilepage/user-id/3960976) ,

welcome to the community!

I think the main problem is you are using single quotes - The JSON standard requires double quotes.

Try to change it like this:

```
{
    "component": {
        "name": "placeholder",
        "showcase": false,
        "only_show_if_degraded": false,
        "description": "placeholder",
        "status": "operational"
    }
}
```

comments: author: Patrick Rutledge
body: Thank you so much for your response. Ok actually I think its something wrong with python. I will try some different things.


author: Patrick Rutledge
body: Ok you lead me down the correct path I fixed it like this (in python):

response = requests.post(spioURL + url, headers=head, data=json.dumps(payload))


Tags: api

component

rest-api
Do you have to be on a specific type of account to have Audience Specific Groups or Members?
Asked by Danny Warburton:

I can;t see how to add Audience specific groups or members and I'm not sure its available under my current account limits.

I'd like to be able to set up users but not have them auto subscribed to any groups. I want them to add themselves and push them to be self sufficient in this and thought Audience specificity would be the way to go


Answers:
author: Zach
body: Hey there Danny

Audience Specific page access groups, and page access users, are only going to be available on an Audience Specific plan type. You can also create an Audience Specific trial page any time you'd like if you want to test out the functionality offered for that specific page type.

If you're wanting for your page users to only have access to certain components, then an Audience specific page could very well be what you're looking for! Page Access users can be created by admins in the management portal, using a CSV importer, or via the API. They will receive an email notification inviting them to create a password. Once in the page they can then select the 'subscribe to updates' button to modify their subscription.

Let me know if this is along the lines of whaty ou are looking for!

Cheers
Can components default to un-selected for new subscribers?
Asked by Alec Hill:

In an effort to drive our customers to select components that are relevant to them vs defaulting to all, we are hoping there is an option to have the components default to un-selected when a new subscriber subscribes. Is that possible?


Answers:
author: Bart van Manen
body: I would also really like an option to set default subscription options for new subscribers. I even contacted Statuspage.io support, but they said there is no such option at the moment and closed the request. Not sure if this is on the backlog somewhere now...


author: Chris Batt
body: +1 for this being a feature request. We need a variety of Components, but some don't apply to all users. Some users only wish to be notified on the status of one component. We really can't rely on users knowing to deselect the right components and we risk the integrity of the alerts by sending noise/alerts that don't concern the users.

comments: author: Kel Hill
body: Definitely required as a control managed internally. As you point out, we cannot rely on users knowing to deselect the right components!


author: Dudi Glasswien
body: +1 Is it so complex to add a setting by default and not auto-select all the components when subscribing? I'm just asking if that is in your backlog.


author: Zach
body: Hey Alec

While there isn't a default option in the admin portal, there is the option for your page subscribers to select the 'Select None' option when creating/tuning their subscription.

From there they could go through the list of components to only select those that are relevant to them.

comments: author: Wasila Rabbani
body: is it possible to un-select components in CSV file when we import it?


author: Bart van Manen
body: Yes, when you import contacts you can decide which components they should be subscribed to. You add the components separated by semi-colon (;) at the end of the line for each subscriber.
New component has no subscribers
Asked by Sophie Reynolds:

Hi

I needed to add a new component for an incident but noticed that the subscribers were not auto-subscribed to it? I am sure that previously when a new component was added it was automatically ticked on the subscribers list?

As it was quite a pressing issue I had to modify a previous component that we had hardly used instead which isn't ideal.

To add a new component in future would I have to export the subscribers and bulk upload them back in with the added component code?

Thanks,

Sophie


Answers:
author: Bart van Manen
body: It's not the most user friendly option, but you could export all your contacts, edit the contact subscriptions in Excel, and then import the contacts again.

Note that you can also set a value in the import sheet to determine if all your subscribers are notified of the new subscriptions or not.

comments: author: Sophie Reynolds
body: Thanks, This is the way I've been doing it. Was hoping for a simpler option!


author: Alec Hill
body: How do we bump this? Can there be an option added for subscribers to choose whether they're added to newly created components?
Why does it say "No incidents or maintenance related to this downtime."?
Asked by Peter Oh:

What needs to be done for the downtime bar to show the related incident instead of showing "No incidents or maintenance related to this downtime"?

We recently added new components to better reflect the downtime with past incidents on our StatusPage. While the days where the incidents happened are showing up as downtime (bars) for the different components, it doesn't show the related incident when I hovered over the downtime bar for the respective components.

Any thoughts?


Answers:
author: Nick Coates
body: Hi Peter,

Welcome to the Atlassian Community! I'm Nick from the Broadcom team (long-time Statuspage customer).

In order for 'related incidents' to be shown on the Uptime Showcase, you must select a component during the incident creation. If these are newly added components then you will not be able to add them to the previous incidents. You can modify the actual uptime avialability but not after-the-fact incidents.

Hope this helps.

Thanks,  
Nick Coates  
Product Owner - Service Status, Broadcom Inc

comments: author: Peter Oh
body: Hi Nick

Thanks for your reply, that makes sense.

-Peter


author: Kumar Venkataraman
body: Looks like the related incident can be shown (only) for a manual incident creation. I have a component that is integrated with PagerDuty and I wonder if there is any way I can get any of the moustache tags to show up as a related incident (or as an annotation, for the bar).

Kumar
How do I add a "Product Release Notes" Section
Asked by David_Hacking:

I know that it is possible to add a Product Release Notes section similar to this page - <https://status.webroot.com/> - but I can't find where to add it to the page. Any suggestions?

Thanks,

-David


Answers:
author: Zach
body: Hey David,

While this isn't something in the scope of support, I was able to find that that page is using some custom JS to create the section you're looking for.

The code for it would look something like the below, you will just need a page on a plan that supports the use of custom Javascript

```
<script>
$('.incidents-list').prepend('<p><a class="font-largest no-link" style="display:block;">PRODUCT RELEASE NOTES</a><br>Click one of these links for detailed release notes<br><a href="https://www.something.com/support/release-notes" target="_blank">Something</a>&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;<a href="https://www.something.com/support/support-consumer-release-notes" target="_blank">Home &amp; Something else</a></p><br><br>');
</script>
```

Hopefully this helps!

comments: author: David_Hacking
body: That is what I needed. Thank you!!


author: Denae Fernandez
body: where exactly would we place this code?


author: Zach
body: [@Denae Fernandez](/t5/user/viewprofilepage/user-id/5025784) you'd need to place it in the custom header/footer section

![2022-12-20_13-42-07.png](https://community.atlassian.com/t5/image/serverpage/image-id/231439iFB18201DAA83E49F/image-size/large?v=v2&px=999 "2022-12-20_13-42-07.png")
Remove DNS Config Banner
Asked by Jimmy Brancaccio:

Greetings!

I setup a trial Statuspage.io page and added a send from email address. I then moved the page over the free plan which doesn't allow for this functionality. Unfortunately I still see the orange/yellow banner saying:

"Before we can send notifications from your custom notifications 'from' email, the DNS config page needs your attention."

How can this banner be removed?

Thanks!


Answers:
author: Nick Coates
body: Hi Jimmy,

I think you'll need to remove the 'FROM' address but if you're on the free plan it may be disabled. If that is the case, I recommend raising a ticket with the Support team to ask them to remove this for you: <https://support.atlassian.com/contact/>

Thanks,  
Nick Coates  
Product Owner - Service Status, Broadcom Inc.

comments: author: Jimmy Brancaccio
body: Hey Nick,

Sounds like a plan. I didn't even know I could still submit tickets since this specific status page was on the free plan. Ticket submitted. ??

Thanks,