General settings
Coralogix gathers your team's preferences onto a single page. Some of them are yours alone, such as your time zone and your personal homepage. Others belong to the whole team, such as the team URL and the alphabetical order Coralogix uses when it sorts text, and a change to one of those reaches every member.
The page shows you the settings your role gives you access to. A setting you cannot view is absent from the page rather than shown as unavailable, and a setting you can view but not change is visible and inactive.
What you need
- To change your personal settings, such as your time zone, date format, and personal homepage, you need
USER-SETTINGS:UPDATECONFIG(included in all standard roles). - To change a team setting, such as the team name and URL, the team homepage, or Default sorting, you need the team permission that governs it. See Permissions.
Set your preferences
Select Settings, then Preferences.
Change your team name and URL, and tell your teammates about the change.
Change your time zone from local time to GMT. This affects all UI views.
Change your time format. This affects all your UI views.
Select the day your week starts on, Monday or Sunday.
This setting is not yet applied across the whole platform. A calendar that has not adopted it keeps the day it starts on today.
Customize the default homepage to be displayed when you access the Coralogix platform or navigate to it from another location in the UI.
- As an admin, define the default homepage for all of your team members. In the Team-level default homepage section, select from the list of most-frequently accessed pages of the Coralogix UI. In addition, in the User-level default homepage section, you can define your personal homepage. This selection overrides the team-level default homepage setting for a specific user.
- As a user, define your personal default homepage by selecting it from the list of most frequently accessed pages of the Coralogix UI. This selection overrides the team-level default homepage setting for a specific user.
In Default sorting, select Case-insensitive or Case-sensitive to set the alphabetical order Coralogix uses when it sorts text. See Default sorting.
Default sorting
This feature is available for early-access customers. To request access and confirm your organization meets the feature criteria, contact your account representative or Support.
Real telemetry does not arrive with a single naming convention. One team instruments a service as API, another as api, a third ships host names in title case. Sorted case-sensitively, those values scatter: every capitalized value lands ahead of every lowercase value, so API sits at the top of a list and api sits halfway down it.
Default sorting lets a team decide which alphabetical order Coralogix uses. Each team sets a single mode, your choice applies to everyone on the team, and it takes effect the next time Coralogix sorts a list.
How each mode orders values
Both modes sort alphabetically. They differ in what they do with capital letters.
Case-sensitive puts every capitalized value ahead of every lowercase value. This is the order Coralogix has always used, and it stays the default.
Case-insensitive groups values by letter and ignores capitalization, so values spelled the same way stay next to each other. Within a group, uppercase comes first: Apple precedes apple.
A service column holding Frontend, backend, Backend, api, and API sorts like this:
| Case-sensitive | Case-insensitive |
|---|---|
API | API |
Backend | api |
Frontend | Backend |
api | backend |
backend | Frontend |
Case-sensitive pushes API and api apart, and separates Backend from backend by further still. Case-insensitive keeps each pair adjacent, which is usually what you want when both spellings describe the same service.
The modes also disagree on values that share no letters at all. Sorting Zebra and apple puts Zebra first in case-sensitive mode, because capital letters come first, and apple first in case-insensitive mode.
Case-insensitive sorting reads accented characters as their base letter, so Éclair sorts between apple and zebra.
Where the setting applies
The mode is cross-platform. Every page that sorts text follows the team's choice, so a table column, a widget label, a chart legend, or a dropdown of values reads the same way wherever it appears in Coralogix. Setting it once covers the whole product, and there is nothing to configure per dashboard, per screen, or per user.
For example:
- Table columns and grouped results in Custom Dashboards, Visual Explorer, Explore, and Infrastructure Monitoring.
- Widget labels and chart legends on bar, pie, gauge, hexagon, stat card, and line chart widgets.
- Dashboard variable values and filter option lists.
- List columns in Alerts management, Cases, and suppression rules.
Visual Explorer draws its tables with the same widget as Custom Dashboards, so it follows the team's mode without any setting of its own.
Match the order a query returns
Each mode mirrors a DataPrime ordering. A column you sort by selecting its header and the same field ordered in a query come back in the same sequence, so a dashboard and the query behind it agree.
| Mode | Equivalent DataPrime clause |
|---|---|
| Case-sensitive | orderby $d.service asc |
| Case-insensitive | orderby toLowerCase($d.service) asc, $d.service asc |
Case-insensitive ordering uses a pair of keys. The first groups values by letter regardless of case. The second keeps values that fold together in a stable order rather than interleaving them run to run.
Values other than text
Sorting applies to text. Numbers, dates, and true/false values keep their natural order in both modes, so a duration column reads 9, 10, 100 rather than grouping by first digit.
Two orderings hold in both modes: empty values come first, and digits come before letters, so 2 precedes Alpha.
Within a text value, Coralogix compares character by character rather than reading runs of digits as numbers. A column holding item1, item2, and item10 reads item1, item10, item2.
A mode belongs to the team, so individual members cannot set a different order for themselves. Members without TEAM-SORTING:READCONFIG do not see the setting, and Coralogix still orders their lists using the team's mode. A column holding a mix of text and numbers orders only the values that share a type, and mixed pairs keep their existing position.
Permissions
Each setting on the page has its own permission. A read permission controls whether the setting appears, and an update permission controls whether you can change it.
| Resource | Description | System roles | API presets |
|---|---|---|---|
TEAM-DOMAIN:MANAGE | Create and modify your team's domain. | Platform Admin | TeamAdmin |
TEAM-DOMAIN:READCONFIG | View your team's domain. | Platform Admin | TeamAdmin |
TEAM-LANDING-PAGE:MANAGE | Define the default homepage for a whole team. | Platform Admin | TeamAdmin |
TEAM-LANDING-PAGE:READCONFIG | View the default homepage for a whole team. | Platform Admin | TeamAdmin |
TEAM-SORTING:READCONFIG | View the team's default sorting mode. | - | - |
TEAM-SORTING:UPDATECONFIG | Set the team's default sorting mode. | - | - |
USER-SETTINGS:READCONFIG | View the user's personal settings, such as the date format and the timezone. | Data Admin, Observability Lead, Platform Admin, Read-Only User, Security User, Standard User | - |
USER-SETTINGS:UPDATECONFIG | Edit the user's personal settings, such as the date format and the timezone. | Data Admin, Observability Lead, Platform Admin, Read-Only User, Security User, Standard User | - |
For the full list, see Permissions list.