Required arguments

Description: Field that contains the values to be used as labels for the data series.

<y-data-field>

Syntax: <field> | <field>, <field>, ...

Description: Field(s) that contains the data to be charted.

Optional arguments

format

Syntax: format=<string>

Description: Used to construct output field names when multiple data series are used in conjuction with a split-by-field. format takes precedence over sep and lets you specify a parameterized expression with the stats aggregator and function ($AGG$) and the value of the split-by-field ($VALUE$).

grouped

Syntax: grouped= true | false

Description: If true, indicates that the input is sorted by the value of the <x-field> and multifile input is allowed.

Default:false

sep

Syntax: sep=<string>

Description: Used to construct output field names when multiple data series are used in conjunctions with a split-by field. This is equivalent to setting format to $AGG$<sep>$VALUE$.

Comments

Ryhluc01
Thank you for the suggestion to add an option to reverse the columns. I will pass that along to our development team. I agree with you that more examples would be useful to understand the xyseries command. We are working to add more examples. Thanks again!

Lstewart splunk, Splunker

July 12, 2019

There needs to be an option to reverse the column order of xyseries. We should also see examples for the the optional arguments because it is unclear how or what they are to be used for.

Ryhluc01

July 2, 2019

Apnetmedic
Thanks for noticing this. The link was on the last phrase in that sentence. I've fixed it now to be on "this walkthrough" which I agree with you would be more clear :-)

Lstewart splunk, Splunker

January 8, 2016

I think there's a link missing? Example 2: Refer to this walkthrough to see how you can combine stats and eval with the xyseries command to create a report on multiple data series.

"this walkthrough" isn't a link, and it seems like it should be, since there's no walkthrough on this page.

xyseries

Enter your email address, and someone from the documentation team will respond to you:

Send me a copy of this feedback

Please provide your comments here. Ask a question or make a suggestion.

Feedback submitted, thanks!

You must be logged into splunk.com in order to post comments.
Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic.
If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk,
consider posting a question to Splunkbase Answers.

0
out of 1000 Characters

Your Comment Has Been Posted Above

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website.
Learn more (including how to update your settings) here »