Which directive is given by the host

If a host goes down, becomes unreachable, or recoveries during a time which is not covered by the time period, no notifications will be sent out. This directive is used to determine when notifications for the host should be sent out. If you specify n none as an option, no host notifications will be sent out. If you do not specify any notification options, Nagios will assume that you want notifications to be sent out for all possible states.

This directive is used to determine whether or not notifications for this host are enabled. This directive determines which host states "stalking" is enabled for.

More information on state stalking can be found here. This directive is used to define an optional string of notes pertaining to the host. If you specify a note here, you will see the it in the extended information CGI when you are viewing information about the specified host. This variable is used to define an optional URL that can be used to provide more information about the host. Any valid URL can be used. If you plan on using relative paths, the base path will the the same as what is used to access the CGIs i.

This can be very useful if you want to make detailed information on the host, emergency contact methods, etc. This directive is used to define an optional URL that can be used to provide more actions to be performed on the host. This image will be displayed in the various places in the CGIs. The image will look best if it is 40x40 pixels in size. This image will be used as the texture map for the specified host in the statuswrl CGI. If it does, the host object will look a bit wierd. This variable is used to define the name of an image that should be associated with this host in the statusmap CGI.

You can leave these option blank if you are not using the statusmap CGI. This variable is used to define coordinates to use when drawing the host in the statusmap CGI. Coordinates should be given in positive integers, as they correspond to physical pixels in the generated image. The origin for drawing 0,0 is in the upper left hand corner of the image and extends in the positive x direction to the right along the top of the image and in the positive y direction down along the left hand side of the image.

For reference, the size of the icons drawn is usually about 40x40 pixels text takes a little extra space. The coordinates you specify here are for the upper left hand corner of the host icon that is drawn. Note: Don't worry about what the maximum x and y coordinates that you can use are. The CGI will automatically calculate the maximum dimensions of the image it creates based on the largest x and y coordinates you specify. This variable is used to define coordinates to use when drawing the host in the statuswrl CGI.

Coordinates can be positive or negative real numbers. The origin for drawing is 0. For reference, the size of the host cubes drawn is 0.

The coordinates you specify here are used as the center of the host cube. This directive is used to define is a longer name or description used to identify the host group.

It is provided in order to allow you to more easily identify a particular host group. This is a list of the short names of hosts that should be included in this group. Multiple host names should be separated by commas. This directive may be used as an alternative to or in addition to the hostgroups directive in host definitions.

This optional directive can be used to include hosts from other "sub" host groups in this host group.

Specify a comma-delimited list of short names of other host groups whose members should be included in this group. This variable is used to define an optional URL that can be used to provide more information about the host group.

This can be very useful if you want to make detailed information on the host group, emergency contact methods, etc. This directive is used to define an optional URL that can be used to provide more actions to be performed on the host group.

This directive is used to specify the short name s of the host s that the service "runs" on or is associated with. Multiple hosts should be separated by commas. This directive is used to specify the short name s of the hostgroup s that the service "runs" on or is associated with. This directive is used to define the description of the service, which may contain spaces, dashes, and colons semicolons, apostrophes, and quotation marks should be avoided.

No two services associated with the same host can have the same description. This directive is used to define an alternate name that should be displayed in the web interface for this service.

This directive is used to identify the short name s of the servicegroup s that the service belongs to. Multiple servicegroups should be separated by commas.

This directive may be used as an alternative to using the members directive in servicegroup definitions. This directive is used to denote whether the service is "volatile". Services are normally not volatile. More information on volatile service and how they differ from normal services can be found here.

By default Nagios will assume that all services are in OK states when it starts. You can override the initial state for a service by using this directive. This directive is used to define the number of times that Nagios will retry the service check command if it returns any state other than an OK state.

Setting this value to 1 will cause Nagios to generate an alert without retrying the service check again. This directive is used to define the number of "time units" to wait before scheduling the next "regular" check of the service.

This directive is used to define the number of "time units" to wait before scheduling a re-check of the service. Services are rescheduled at the retry interval when they have changed to a non-OK state. This directive is used to determine whether or not active checks of this service are enabled.

This directive is used to determine whether or not passive checks of this service are enabled. This directive is used to specify the short name of the time period during which active checks of this service can be made.

This directive is used to determine whether or not freshness checks are enabled for this service. This directive is used to specify the freshness threshold in seconds for this service. This directive is used to specify the short name of the command that should be run whenever a change in the state of the service is detected i. This directive is used to determine whether or not the event handler for this service is enabled.

This directive is used to specify the low state change threshold used in flap detection for this service. This directive is used to specify the high state change threshold used in flap detection for this service. This directive is used to determine whether or not flap detection is enabled for this service. This directive is used to determine what service states the flap detection logic will use for this service.

This directive is used to determine whether or not the processing of performance data is enabled for this service. This directive is used to determine whether or not status-related information about the service is retained across program restarts.

This directive is used to determine whether or not non-status information about the service is retained across program restarts. This directive is used to define the number of "time units" to wait before re-notifying a contact that this service is still in a non-OK state.

If you set this value to 0, Nagios will not re-notify contacts about problems for this service - only one problem notification will be sent out.

This directive is used to define the number of "time units" to wait before sending out the first problem notification when this service enters a non-OK state. This directive is used to specify the short name of the time period during which notifications of events for this service can be sent out to contacts. No service notifications will be sent out during times which is not covered by the time period. This directive is used to determine when notifications for the service should be sent out.

If you specify n none as an option, no service notifications will be sent out. This directive is used to determine whether or not notifications for this service are enabled. This is a list of the short names of the contacts that should be notified whenever there are problems or recoveries with this service.

You must specify at least one contact or contact group in each service definition. This is a list of the short names of the contact groups that should be notified whenever there are problems or recoveries with this service.

This directive determines which service states "stalking" is enabled for. This directive is used to define an optional string of notes pertaining to the service. If you specify a note here, you will see the it in the extended information CGI when you are viewing information about the specified service.

This directive is used to define an optional URL that can be used to provide more information about the service. This can be very useful if you want to make detailed information on the service, emergency contact methods, etc. But it looks hacky, so better to pass the component reference as Input parameter to the directive, as described below.

I tried two solutions from here: Michiel Windey's one using an abstract class as interface for the components where the directive will be used , and Anthony's one using Host Self Optional. Both work with Angular Both are non hacky and are probably future-proof, unlike the hacky solutions using undocumented private fields…. The second one has the advantage to access the existing components without changing them.

But you probably need to have lot of checks and special cases to handle, depending on which component is really injected. The first one has the inconvenience to require the components to be modified, but you can define in the interface abstract class all the fields and methods you are going to use in the directive, and thus you can access them with a single parameter, without needing to check what kind of component is injected.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. How to access host component from directive? Ask Question. Asked 4 years, 2 months ago. Active 17 days ago. Viewed 37k times. Improve this question. AngularChef AngularChef Add a comment. Active Oldest Votes. Improve this answer. Ideally I would need a generic solution that works for any component. In fact you might have a suggestion for what I'm trying to do here: stackoverflow.

Sets the number and size of the buffers used for reading a response from a disk. Enables or disables specifying the port in absolute redirects issued by nginx.

If possible, the transmission of client data will be postponed until nginx has at least size bytes of data to send. The zero value disables postponing data transmission. FreeBSD 7 has to be patched. The number of such redirects is limited. Allows accurate tuning of per-request memory allocations. Enables or disables resetting timed out connections and connections closed with the non-standard code 1.

The reset is performed as follows. The address can be specified as a domain name or IP address, with an optional port 1. If port is not specified, the port 53 is used.

Name servers are queried in a round-robin fashion. By default, nginx will look up both IPv4 and IPv6 addresses while resolving. By default, nginx caches answers using the TTL value of a response.

An optional valid parameter allows overriding it:. The parameter is available as part of our commercial subscription. A path to the file is constructed by merely adding a URI to the value of the root directive. If a URI has to be modified, the alias directive should be used.

In both cases the specified size is used. Sets a timeout for transmitting a response to the client. The timeout is set only between two successive write operations, not for the transmission of the whole response. If the client does not receive anything within this time, the connection is closed.

Starting from nginx 0. On the first read, the FreeBSD kernel loads the first K bytes of a file into memory, although next reads will only load data in 16K chunks. Limits the amount of data that can be transferred in a single sendfile call.

Without the limit, one fast connection may seize the worker process entirely. Sets configuration for a virtual server. Named captures in regular expressions create variables 0. This is the default setting. During searching for a virtual server by name, if the name matches more than one of the specified variants, e.

Detailed description of server names is provided in a separate Server names document. If this field is not present, the IP address of the server is used. Sets the bucket size for the server names hash tables. The details of setting up hash tables are provided in a separate document.

Sets the maximum size of the server names hash tables. The build parameter 1. Additionally, as part of our commercial subscription , starting from version 1. Sets the size of the buffer used for storing the response body of a subrequest. By default, the buffer size is equal to one memory page. This is either 4K or 8K, depending on a platform.

It can be made smaller, however. The directive is applicable only for subrequests with response bodies saved into memory. For example, such subrequests are created by SSI. The option is enabled when a connection is transitioned into the keep-alive state.

The options are enabled only when sendfile is used. Enabling the option allows. Checks the existence of files in the specified order and uses the first found file for request processing; the processing is performed in the current context. The path to a file is constructed from the file parameter according to the root and alias directives. If none of the files were found, an internal redirect to the uri specified in the last parameter is made.

Limits the speed of reading the response from the proxied server. The rate is specified in bytes per second. The zero value disables rate limiting. The limit is set per a request, and so if nginx simultaneously opens two connections to the proxied server, the overall rate will be twice as much as the specified limit.

The limitation works only if buffering of responses from the proxied server is enabled. This directive sets the maximum size of the temporary file. Specifies the HTTP method to use in requests forwarded to the proxied server instead of the method from the client request. One should bear in mind that passing a request to the next server is only possible if nothing has been sent to a client yet.

That is, if an error or timeout occurs in the middle of the transferring of a response, fixing this is impossible. The directive also defines what is considered an unsuccessful attempt of communication with a server. Passing a request to the next server can be limited by the number of tries and by time. Limits the time during which a request can be passed to the next server.

The 0 value turns off this limitation. Limits the number of possible tries for passing a request to the next server. Defines conditions under which the response will not be saved to a cache.

Sets the protocol and address of a proxied server and an optional URI to which a location should be mapped. The address can be specified as a domain name or IP address, and an optional port:. If a domain name resolves to several addresses, all of them will be used in a round-robin fashion.

In addition, an address can be specified as a server group. Parameter value can contain variables. In this case, if an address is specified as a domain name, the name is searched among the described server groups, and, if not found, is determined using a resolver. WebSocket proxying requires special configuration and is supported since version 1. Permits passing otherwise disabled header fields from a proxied server to a client.

Defines a timeout for reading a response from the proxied server. The timeout is set only between two successive read operations, not for the transmission of the whole response. If the proxied server does not transmit anything within this time, the connection is closed. Hence, the two configurations below are equivalent:. The directive can be specified 1.

If several directives can be applied to the header fields of a proxied server response, the first matching directive will be chosen. Using this directive, it is also possible to add host names to relative redirects issued by a proxied server:. When buffering is enabled, the entire request body is read from the client before sending the request to a proxied server. When buffering is disabled, the request body is sent to the proxied server immediately as it is received. In this case, the request cannot be passed to the next server if nginx already started sending the request body.

Sets a timeout for transmitting a request to the proxied server.