All Apps and Add-ons

PAVO Getwatchlist Add-on - names of additional fields?

kcima
Engager

I am testing PAVO Getwatchlist Add-on 1.1.7 on Splunk Enterprise 9.0.0
It looks working almost fine. I need to use additional columns and set configration in getwatchlist.conf like following.

1=additional1
2=additional2
3=additional3
...

I expected that field name of additional columns become "additional1", "additional2" ... But, it became "1", "2", ...

I have tried to modify getwatchlist.py like following.

$ diff getwatchlist.py getwatchlist_fix.py
388c388
< row_holder[add_col] = self.format_value(row[int(add_col)])
---
> row_holder[add_cols[add_col]] = self.format_value(row[int(add_col)])

After that, the field names became "additional1", "additional2" ... as expected.
I am not sure which behavior is correct. But, I feel "additional1", "additional2" ... are better.

Labels (1)
0 Karma
1 Solution

kcima
Engager

I have tried ver 1.2.0 and could get csv header and fields with following SPL.

| getwatchlist csv url=https://.../xx.csv

This is what I needed! Thank you so much!

View solution in original post

0 Karma

kcima
Engager

I have tried ver 1.2.0 and could get csv header and fields with following SPL.

| getwatchlist csv url=https://.../xx.csv

This is what I needed! Thank you so much!

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...