# Pie Chart Visualization

Upon selecting the ***Pie Chart*** visualization type for log records, the **Total Events** section below will display a circle graph with the corresponding legend positioned beside it, representing information based on the [Time Range](/product-docs/service-menu/logs/time-range.md) you’ve set in the top right corner of the *Logs* panel. 

<figure><img src="https://lh7-us.googleusercontent.com/mHp-NFWOf0LGazdzIaifw2LNuy7jYE24MwGgbVMf7rkdsU2ZcsqX7qP9j4eSJejyDHQ3rlAXJyZFUHhYUJkF9GTJDMMtOfRPjrc2_WqigQ8o0Xrwjl6-AeWLz5Iwby116dVnkFsUgYy7SRsgfCRp5UI" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
For now, this visualization type is available for ***Delivery*** events only. It will be expanded to cover other event types in the upcoming releases.

To get more space for investigating this graph, use the ***Options > Service Time*** switch in the top right corner to conceal the upper plot.
{% endhint %}

This data representation mode provides extended capabilities for intricate data analysis by means of advanced grouping options that appear under the visualization selection row upon choosing this display type.&#x20;

<figure><img src="https://lh7-us.googleusercontent.com/i9kKXcu7FTIXpsCMRckYKNtZjICH-6iMookenpvJZuZf5WRu4QmX5P_bcEGbE5b7cm3JwbergTSt9wGMTs2wnMMXgYcvz6hQYs1Soy39cQC5sg-6JY0ynixfS9UKzK8Tyj8NdrUIBLQDmzHZOxzjfcc" alt=""><figcaption></figcaption></figure>

\
There are 2 types of data management controls here:

* **Group into** - defines the entity by which the data should be grouped (currently, only the *fields* selection is available here; advancement is coming soon)
* **Show** - grouping parameters of the following structure:
  * ***Count unique*** - an expandable list, with the ability to choose an item or attribute that will be tallied uniquely within the given data set:
    * *client\_ip* - to count unique IPs the requests came from&#x20;
    * *client\_city* - to count specific locations the requests came from
    * *client\_country\_code* - to count distinct countries the requests came from
    * *cache\_status* - to count particular requests’ cache statuses (TCP\_HIT, TCP\_MISS, CONFIG\_NOCACHE, etc)
    * *client\_as\_org* - to count unique networks or organizations the requests came from&#x20;
    * *client\_isp* - to count unique Internet Service Providers the requests came from
    * *user\_agent* - to count unique User-Agent request headers
    * *host* - to count unique requested application hostnames
    * *method* - to count request methods (GET, POST, HEAD, etc)
    * *path* - to count requested application assets
    * *pop* - to count ADN/CDN points of presence the requests were delivered from
  * ***by*** - defines the parameter for grouping the events sorted upon the *Count unique* condition; the given list of options includes all the items mentioned above plus a set of additional ones as follows:
    * *client\_asn* - to group requests by the network’s or organization’s Autonomous System Number (ASN)&#x20;
    * *status\_code* - to group requests by the request status code (200, 201, 202, etc)
    * *waf\_audit\_alert* - to group requests by true/false value of the boolean that indicates triggering of the WAF Audit mode alert
    * *waf\_prod\_action* - to group requests by true/false value of the boolean that indicates triggering of the WAF Block mode alert for production profiles
    * *waf\_prod\_alert* - to group requests by true/false value of the boolean that indicates triggering of the WAF Audit mode alert for production profiles
    * *rl\_alert* - to group requests by true/false value of the boolean that indicates triggering of the Rare Limiting alert

You can add as many additional ***by*** parameters as you need to.

Also, by using a separate ***limit to*** control on the right, you can define the number of groups to display - either *top 10*, *top 20*, or *top 50* - ranged based on the number of included results.

<figure><img src="https://lh7-us.googleusercontent.com/XZJ9d3T2JPk0zueeH8s2jIoKMzaElm_5jenL1h2OVUbEvSDGvKNwF33hjYcZSYjCLANT5jQjlfG3Mmc3ecvMcV7x8LBNBKF8-2D4OTPuXSOffq9yWau0smYZnhZ8pAQ_Gvjz3ibVIs8KnMLP6kN9hiU" alt=""><figcaption></figcaption></figure>

After applying all desired grouping filters, the data within the circle graph is aggregated accordingly, where each pie sector is represented by a distinct color.

<figure><img src="https://lh7-us.googleusercontent.com/UFYt6sTNYF1dAp3bTi1nu5UCkyG0m1j-M--O3LeUGg3Fd55e-db1Ne_RPzxPerxzoUG1JLwx-funuqGhP6tMQUJsCePAFOF4Yewn7Z137r-NBzY9KH4tR5hbdsshxuvRAkrfJlheEEqzKwGKVZY3Bjc" alt=""><figcaption></figcaption></figure>

\
Hover over any of the colored pie sectors to view information about its label (i.e. the last ***by*** parameter value) and the number of records included based on your set grouping filters.<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.edgeport.com/product-docs/service-menu/logs/total-events-section/pie-chart-visualization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.