Difference between revisions of "Application"
m (→Overview) |
m |
||
| Line 2: | Line 2: | ||
== Overview == | == Overview == | ||
| − | Applications are | + | Applications are the means by which Veloopti keeps data, dashboards, actions and policies segregated within an organisation. Applications in your organisation are found by clicking on the Application menu item at the top of the Veloopti console. Applications can be made a [[Favourites|favorite]] in the same manner as as dashboards are for quicker access to them. |
| + | == Selecting an application == | ||
| + | Clicking on the Application menu item brings up the [[Application_view|application view]]. | ||
| − | === | + | === Navigating applications === |
| − | :'' | + | The easiest way to navigate through your applications is to change the application through the breadcrumb. Use the drop down application menu [[file:Breadcrumb application navigation selection arrow.png|20px]] to select the other applications that you have access to. |
| − | + | ||
| + | The below example contains an application called ''Application of Amazing things''. You can use the drop down menu to the right of the application name to select another. | ||
| + | |||
| + | [[file:Breadcrumb application navigation.png|500px]] | ||
| + | |||
| + | === Navigating components of an application === | ||
| + | |||
| + | The below example shows the nodes of the ''Application of Amazing things''. Use the drop down menu to the right of the Node item to select between actions, dashboards, nodes, permissions, policies roles or users. | ||
| + | |||
| + | [[file:Breadcrumb application navigation.png|500px]] | ||
| + | |||
| + | == Components of an application == | ||
| + | Components of an application are able to be viewed and configured depending upon your permissions. | ||
| − | === Dashboards === | + | === Visible to all application users === |
| + | ==== Dashboards ==== | ||
:''{{See also|Dashboard}}'' | :''{{See also|Dashboard}}'' | ||
Dashboards can be created for the nodes in the application from the policies or API that are collecting metrics. | Dashboards can be created for the nodes in the application from the policies or API that are collecting metrics. | ||
| − | === Nodes === | + | ==== Nodes ==== |
:''{{See also|Node}}'' | :''{{See also|Node}}'' | ||
Nodes that have been added to the application appear here. Nodes are able to have application policies deployed to them, application actions associated with them and their metrics can be visible for display in a dashboard. | Nodes that have been added to the application appear here. Nodes are able to have application policies deployed to them, application actions associated with them and their metrics can be visible for display in a dashboard. | ||
| − | === Permissions === | + | ==== Users ==== |
| + | :''{{See also|User}}'' | ||
| + | Once a user is added to the application they are able to be added to roles within the application. | ||
| + | |||
| + | === Visible only with appropriate permissions === | ||
| + | ==== Actions ==== | ||
| + | :''{{See also|Action}}'' | ||
| + | Actions are command line applications or commands that can be run on a server with a Veloopti agent. The application or command can return a result that will be displayed back to you after it is completed. | ||
| + | |||
| + | ==== Permissions ==== | ||
:''{{See also|Permission}}'' | :''{{See also|Permission}}'' | ||
| − | Roles can be created | + | Roles can be created or deleted with permissions applied to the role. After selecting a role permissions can be enabled or disabled. |
| − | === Policies === | + | ==== Policies ==== |
:''{{See also|Policy}}'' | :''{{See also|Policy}}'' | ||
| − | [[Glossary_of_terms#P|Policies]] can be created, modified and deleted | + | [[Glossary_of_terms#P|Policies]] can be created, modified and deleted. After being created policies are put into a policy group that can be associated with a node group for deployment. |
| − | === Roles == | + | ==== Roles ==== |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
:''{{TNT|Main|Application roles}}'' | :''{{TNT|Main|Application roles}}'' | ||
| − | + | The one or more roles that you have in an application determines the items presented that you are to perform. Everyone is able to see all events, users and nodes in an application. From here your role determines any additional permissions that you may have. There are five default roles available within an application. | |
| − | The | ||
{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;" | {| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;" | ||
| Line 45: | Line 60: | ||
| Owner || There is one owner for each application. Along with the Application Administrator they are able to rename and delete the application. The owner and Application administrator is also able to grant and remove anyrole or notification group to another user of the application. | | Owner || There is one owner for each application. Along with the Application Administrator they are able to rename and delete the application. The owner and Application administrator is also able to grant and remove anyrole or notification group to another user of the application. | ||
|- | |- | ||
| − | | Administrator || Can do anything in | + | | Administrator || Can do anything in the application that involves: users, policies, actions, events and notifications. |
|- | |- | ||
| Power user || Power users are able to do everything the [Application name] Administrator can do except for: | | Power user || Power users are able to do everything the [Application name] Administrator can do except for: | ||
| Line 51: | Line 66: | ||
| Operator || The date/time that the message will be removed from your message inbox | | Operator || The date/time that the message will be removed from your message inbox | ||
|- | |- | ||
| − | | | + | | Read only || Has read only access to see dashboards and events. |
|} | |} | ||
Revision as of 23:26, 6 December 2017
1 Overview
Applications are the means by which Veloopti keeps data, dashboards, actions and policies segregated within an organisation. Applications in your organisation are found by clicking on the Application menu item at the top of the Veloopti console. Applications can be made a favorite in the same manner as as dashboards are for quicker access to them.
2 Selecting an application
Clicking on the Application menu item brings up the application view.
The easiest way to navigate through your applications is to change the application through the breadcrumb. Use the drop down application menu 
to select the other applications that you have access to.
The below example contains an application called Application of Amazing things. You can use the drop down menu to the right of the application name to select another.
The below example shows the nodes of the Application of Amazing things. Use the drop down menu to the right of the Node item to select between actions, dashboards, nodes, permissions, policies roles or users.
3 Components of an application
Components of an application are able to be viewed and configured depending upon your permissions.
3.1 Visible to all application users
3.1.1 Dashboards
- See also: Dashboard
Dashboards can be created for the nodes in the application from the policies or API that are collecting metrics.
3.1.2 Nodes
- See also: Node
Nodes that have been added to the application appear here. Nodes are able to have application policies deployed to them, application actions associated with them and their metrics can be visible for display in a dashboard.
3.1.3 Users
- See also: User
Once a user is added to the application they are able to be added to roles within the application.
3.2 Visible only with appropriate permissions
3.2.1 Actions
- See also: Action
Actions are command line applications or commands that can be run on a server with a Veloopti agent. The application or command can return a result that will be displayed back to you after it is completed.
3.2.2 Permissions
- See also: Permission
Roles can be created or deleted with permissions applied to the role. After selecting a role permissions can be enabled or disabled.
3.2.3 Policies
- See also: Policy
Policies can be created, modified and deleted. After being created policies are put into a policy group that can be associated with a node group for deployment.
3.2.4 Roles
- Main article: Application roles
The one or more roles that you have in an application determines the items presented that you are to perform. Everyone is able to see all events, users and nodes in an application. From here your role determines any additional permissions that you may have. There are five default roles available within an application.
| Default application roles | |
|---|---|
| Role | Description |
| Owner | There is one owner for each application. Along with the Application Administrator they are able to rename and delete the application. The owner and Application administrator is also able to grant and remove anyrole or notification group to another user of the application. |
| Administrator | Can do anything in the application that involves: users, policies, actions, events and notifications. |
| Power user | Power users are able to do everything the [Application name] Administrator can do except for: |
| Operator | The date/time that the message will be removed from your message inbox |
| Read only | Has read only access to see dashboards and events. |