servicepulse message details and menu organisation #7098
Conversation
| #### For Administrators |
There was a problem hiding this comment.
It may be better to referring to the 2 different stake holders as Developers and Operations
There was a problem hiding this comment.
this text is taken from ServiceInsight documentation... system Administrators could belong to Operations, but that's making big assumptions about the customer's structure
There was a problem hiding this comment.
I fail to see the benefits of a "real-world" scenario in this image. As it currently is, the functionality of the diagram is displayed
| @@ -30,14 +35,16 @@ SC[ServiceControl]-- HTTP API & SignalR ---SP | |||
| SCM[Monitoring]-- HTTP API ---SP[ServicePulse] | |||
| ``` | |||
|
|
|||
| ## System status overview | |||
| ## ServicePulse views | |||
There was a problem hiding this comment.
"views" ? are these features?
There was a problem hiding this comment.
no? They're tabs. I just needed a parent heading so that the right-side navigation wasn't messed up
Co-authored-by: John Simons <[email protected]>
|
The troubleshooting section, belongs either in "introduction" or on its own. In SC it is on its own. |
for updated message details view based on ported SI functionality