Skip to main content

Purge Logging Analytics logs

 Is your tenant generating unexpected costs for Logging Analytics? Here is a possible solution.

In the metrics you can see that as time progresses the storage used by Logging Analytics only increases.


The explanation is that you are only generating logs, without deleting the old ones. Here is how you can create a Logging Analytics log purging policy:

Navigate to Logging Analytics / Administration / Storage


Here you can create a policy like this, which will purge the logs with more than 1 month old (for example):


Also you can delete manually the Logging Analytics logs clicking the following button:









Popular posts from this blog

Subnets

  A few days ago, in the previous post, we saw how to create a VCN. Today we are going to see how to create a subnet. A subnet is nothing more or less than a division of the VCN. A subnet can be contained in a single AD or be common to the entire region (recommended option). To deploy a DB or a compute instance, it is necessary to have previously created a subnet, to place it there and to take an IP within its range. It is also important to note that within the same VCN, the IP ranges of the subnets cannot overlap. A subnet can be public if you want to present the resources to the Internet or private if you do not. To access these resources, resources such as bastions, VPNs or Fastconnect must be used. In later posts we will go into more detail about all of these pieces in more detail. As usual, we are going to look at different ways of creating a VCN in OCI: Manually from OCI Console Access a previously created VCN, in which we want to deploy the subnet. In the subn...

Compute instances

In today's post, we are going to talk about compute instances in OCI. First of all, what is a compute instance? A compute instance is the OCI resource that you must deploy to provision and manage compute hosts. So, If you have the requirement to create a Virtual Machine (VM) or an infrastructure to host your application then you must use Compute Instance service. OCI offers 2 flavours: Bare Metal: Physical server without any virtualisation. Direct access to the hardware. The user has to manage the virtualisation layer, as well as the rest of the layers: OS, App Container, code... It is  a Single-Tenant Model, i.e. dedicated to only one client. It does not share hardware with other clients. Virtual Machine: It is basically a Bare metal with a virtualisation layer (which is taken care of by the Cloud Provider). Therefore, it has a hypervisor where it can run VMs smaller than the BM. It is based on a Multi-Tenant model. OCI also offers different shapes depending on the requi...