[comment]: # translation:outdated

[comment]: # ({b6bdd5f4-cd4a930c})
# sla.update

[comment]: # ({/b6bdd5f4-cd4a930c})

[comment]: # ({new-79afe9b7})
### Description

`object sla.update(object/array slaids)`

This method allows to update existing SLA entries.

::: noteclassic
This method is only available to *Admin* and *Super admin*
user types. Permissions to call the method can be revoked in user role
settings. See [User
roles](/manual/web_interface/frontend_sections/administration/user_roles)
for more information.
:::

[comment]: # ({/new-79afe9b7})

[comment]: # ({new-5fb5ebb3})
### Parameters

`(object/array)` SLA properties to be updated.

The `slaid` property must be defined for each SLA, all other
properties are optional. Only the passed properties will be updated, all
others will remain unchanged.

Additionally to the [standard SLA properties](object#sla), the
method accepts the following parameters.

| Parameter           | [Type](/manual/api/reference_commentary#data_types) | Description                                                                                                                                                            |
|---------------------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| service\_tags       | array                                               | SLA [service tags](/manual/api/reference/sla/object#sla-service-tag) to replace the current SLA service tags.<br><br>At least one service tag must be specified.       |
| schedule            | array                                               | SLA [schedule](/manual/api/reference/sla/object#sla-schedule) to replace the current one.<br><br>Specifying parameter as empty will be interpreted as a 24x7 schedule. |
| excluded\_downtimes | array                                               | SLA [excluded downtimes](/manual/api/reference/sla/object#sla-excluded-downtime) to replace the current ones.                                                          |

[comment]: # ({/new-5fb5ebb3})

[comment]: # ({102d483b-9465ee4d})
### Valori di ritorno

`(object)` Restituisce un oggetto contenente gli ID degli SLA aggiornati
sotto la proprietà `slaids`.

[comment]: # ({/102d483b-9465ee4d})

[comment]: # ({b41637d2-b41637d2})
### Esempi

[comment]: # ({/b41637d2-b41637d2})

[comment]: # ({new-b9918036})
#### Updating service tags

Make SLA with ID "5" to be calculated at monthly intervals for NoSQL related services,
without changing its schedule or excluded downtimes; set SLO to 95%.

Request:

``` {.java}
{
    "jsonrpc": "2.0",
    "method": "sla.update",
    "params": [
        {
            "slaid": "5",
            "name": "NoSQL Database engines",
            "slo": "95",
            "period": 2,
            "service_tags": [
                {
                    "tag": "Database",
                    "operator": "0",
                    "value": "Redis"
                },
                {
                    "tag": "Database",
                    "operator": "0",
                    "value": "MongoDB"
                }
            ]
        }
    ],
    "auth": "038e1d7b1735c6a5436ee9eae095879e",
    "id": 1
}
```

Response:

``` {.java}
{
    "jsonrpc": "2.0",
    "result": {
        "slaids": [
            "5"
        ]
    },
    "id": 1
}
```

[comment]: # ({/new-b9918036})

[comment]: # ({new-263b1baa})
#### Changing the schedule of an SLA

Switch the SLA with ID "5" to a 24x7 schedule.

Request:

``` {.java}
{
    "jsonrpc": "2.0",
    "method": "service.update",
    "params": {
        "slaid": "5",
        "schedule": []
    },
    "auth": "038e1d7b1735c6a5436ee9eae095879e",
    "id": 1
}
```

Response:

``` {.java}
{
    "jsonrpc": "2.0",
    "result": {
        "slaids": [
            "5"
        ]
    },
    "id": 1
}
```

[comment]: # ({/new-263b1baa})

[comment]: # ({new-d4685b1d})
#### Changing the excluded downtimes for an SLA

Add a planned 4 hour long RAM upgrade downtime on the 6th of April, 2022,
while keeping (needs to be defined anew) a previously existing software upgrade planned on the 4th of July
for the SLA with ID "5".

Request:

``` {.java}
{
    "jsonrpc": "2.0",
    "method": "service.update",
    "params": {
        "slaid": "5",
        "excluded_downtimes": [
            {
                "name": "Software version upgrade rollout",
                "period_from": "1648760400",
                "period_to": "1648764900"
            },
            {
                "name": "RAM upgrade",
                "period_from": "1649192400",
                "period_to": "1649206800"
            }
        ]
    },
    "auth": "038e1d7b1735c6a5436ee9eae095879e",
    "id": 1
}
```

Response:

``` {.java}
{
    "jsonrpc": "2.0",
    "result": {
        "slaids": [
            "5"
        ]
    },
    "id": 1
}
```

[comment]: # ({/new-d4685b1d})

[comment]: # ({099777f0-fd1b6894})
### Fonte
 
CSla::update() in *ui/include/classes/api/services/CSla.php*.

[comment]: # ({/099777f0-fd1b6894})