Multiple Auto registration actions

[Captain_Paralytic]

As well as certain basic templates that all hosts will have, some extra templates need to be added based on the purpose of the host. Is there any way to have multiple auto registration actions fire or is there a way to make sure that the "best match" action is the one that fires?

[Collateral]

+1 on this post. I am also curious as to what priority is given to auto-registration actions, i.e. Once a condition is satisfied, do the other actions get ignored? Or do all applicable actions take place if true?

[Collateral]

I tested this out for myself and it turns out it applies all the Actions that it matches during Auto-Registration. Hopefully that answers your question Captain_Paralytic

[Captain_Paralytic]

Hi Collateral

When I tried it , it didn't seem to. I had the actions set up so that one of them was to add the host, add to a couple of generic hoist groups and link to a couple of generic templates. The second one was to add another template and this did not happen. Now that MAY have been because the second one ran before the one that added the host did.

What operations did your multiple actions perform?

[kloczek]

If you need assign more than one template you don't need multiple actions.
Just add use more templates in single action.

[Collateral]

Thanks kloczek !

Captain_Paralytic My use case scenario calls for multiple actions. After separating between servers and LXC containers (looking for host names with or without LXC) , we use these containers for varying tasks. For example, we will have separate containers running Redis and separate containers running Logstash. These containers are named suitably after their purpose (redis-container-1.lxc). We use actions to add hosts to different host groups and to link to different templates.

[kloczek]

I'm not entirely sure am I understand you.
Are you using the same container to run sequentially different applications/services?
Please describe a bit more precisely what you are doing and with what you have problem on using zabbix as monitoring tool.

[r00am]

Hello, I am interested in the same topic (created an account just to ask the same question).

I was thinking we could use multiple actions to have some separation of concerns (e.g. an action for checking if it's a Linux machine and has correct secret, another to assign specific templates for Databases, Services, Web, etc...).

My primary goal is to automate as much as possible the process of adding a new server. After auto registration, I would like to avoid adding manually specific host groups and templates.

PS: I am using Zabbix 4.0.3