magma-orc8r-eventd
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 31 | 30 May 2023 | |
| latest/stable | 23 | 07 Mar 2023 | |
| latest/beta | 16 | 08 Sep 2022 | |
| latest/edge | 30 | 04 May 2023 | |
| latest/edge | 26 | 14 Mar 2023 | |
| 1.8/stable | 31 | 30 May 2023 | |
| 1.8/candidate | 31 | 30 May 2023 | |
| 1.8/beta | 31 | 30 May 2023 | |
| 1.8/edge | 31 | 30 May 2023 | |
| 1.6/stable | 23 | 24 Feb 2023 | |
| 1.6/candidate | 23 | 24 Feb 2023 | |
| 1.6/beta | 23 | 24 Feb 2023 | |
| 1.6/edge | 24 | 08 Mar 2023 |
juju deploy magma-orc8r-eventdService that acts like an intermediary for different magma services, using the service303 interface, it will receive and push the generated registered events to the td-agent-bit service on the gateway, so these can be then later sent to Orchestrator. These events will be sent to ElasticSearch where they can be queried.
Service that acts like an intermediary for different magma services, using the service303 interface, it will receive and push the generated registered events to the td-agent-bit service on the gateway, so these can be then later sent to Orchestrator. These events will be sent to ElasticSearch where they can be queried.