Humio Server 1.0.59 Archive (2018-04-26)
Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | Config. Changes? |
---|---|---|---|---|---|---|---|
1.0.59 | Archive | 2018-04-26 | Cloud | 2020-11-30 | No | 1.1.0 | Yes |
Regular update release.
Requires data migration and configuration changes — Auth0 changes.
Deprecation
Items that have been deprecated and may be removed in a future release.
The configuration options
AUTH0_API_CLIENT_ID
andAUTH0_API_CLIENT_SECRET
have been deprecated in favor ofAUTH0_CLIENT_ID
andAUTH0_CLIENT_SECRET
respectively - the old names will continue to work as aliases.
Behavior Changes
Scripts or environment which make use of these tools should be checked and updated for the new configuration:
Summary
If you are using Auth0 in your on-prem installation of Humio you must update your Auth0 Application configuration and re-configure Humio(or start using your OAuth identity provider directly). We at Humio will be happy to help. Below configuration changes are only relevant if Auth0 is used for authentication:
Fixed in this release
Summary
New convenience syntax for passing the
as
parameter using assignment syntax.minx := min(x)
is equivalent tomin(x, as=minx)
. This can be used at top-level|
between bars|
, or within[
array blocks]
.The parser handles left and right double quotes which can easily occur if you edit your queries in a word processor, i.e.,
Protocol := "UDP - 17"
The Auth0 configuration properties
AUTH0_WEB_CLIENT_ID
andAUTH0_WEB_CLIENT_SECRET
have been removed. You can safely delete the associated Auth0, as Humio only requires on Auth0 Application in the future.New syntax for computing multiple aggregates for example, to compute both min and max
... | [min(foo), max(foo)] | ...
. This syntax is shorthand for thestats()
function.Existing users on cloud.humio.com will need to re-authenticate the application 'humio' to use their account information.
Users that are authenticated through Auth0 will need to configure the
PUBLIC_URL
option, you must add addINI$PUBLIC_URL/auth/auth0
To the list of callback URLs in your Auth0 Application.
New convenience syntax for passing the field= parameter to a function using curly assignment syntax.
ip_addr =~ cidr("127.0.0.1/24")
is equivalent tocidr("127.0.0.1/24", field=ip_addr)
. This can also be used for regex i.e.,name =~ regex("foo.*")
.The configuration option
AUTH0_WEB_CLIENT_ID_BASE64ENC
has been remove.Humio Auth0 no longer requires the grant
read:users
, you can safely disable that on your Auth0 Application - or just leave it.New naming convention for function names is
camelCase()
which is now reflected in documentation and examples. Functions are matched case-insensitively, so the change is backwards compatible.Humio now support authenticating with Google, GitHub and Atlassian/Bitbucket directly (see Authenticating with OAuth Protocol), without the need to go through Auth0. This is part of our GDPR efforts for our customers on cloud.humio.com, so as to avoid more third parties involved with your data than necessary.
Renamed the
alt
keyword tocase
.alt
will still work for a few releases but is now deprecated.Depending on how you set up your Auth0 application, you may need to update your Auth0 Application Type to "Regular Web Application" in the your Auth0 account, more details can be found in our Authenticating with OAuth Protocol documentation.
The
head()
function allows you to do deduplication by usinggroupBy([ field1, field2, ... ], function=head(1))
Functions
The query language has several new functions:
formatTime()
,ipLocation()
,rename()
,splitString()
,parseInt()
(updated version ofto_radix_10
function),stats()
,head()
. See Query Functions documentation for details of each one.